ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Jonathan Corbet <corbet@lwn.net>, Jason Cooper <jason@lakedaemon.net>
Cc: Rob Herring <robh@kernel.org>,
	Linux ARM Kernel <linux-arm-kernel@lists.infradead.org>,
	ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] ARM legacy board DT conversion finalization
Date: Thu, 15 May 2014 13:15:46 +0100	[thread overview]
Message-ID: <20140515121546.3A06AC40B0E@trevor.secretlab.ca> (raw)
In-Reply-To: <20140511083729.211e9b5f@lwn.net>

On Sun, 11 May 2014 08:37:29 -0400, Jonathan Corbet <corbet@lwn.net> wrote:
> On Sat, 10 May 2014 23:00:09 -0400
> Jason Cooper <jason@lakedaemon.net> wrote:
> 
> > So, I'm proposing a session where each sub-arch gives a brief run-down
> > of the status of the legacy board conversion, and wraps up with a todo
> > list.  After all of the sub-arches have given their status (5 - 10
> > minutes each?), we hash out helping each other with the final pieces.
> 
> This *really* looks like an ARM minisummit topic to me; hopefully one
> of those is in the works?

It does, doesn't it? I wouldn't want this as a main ksummit topic.

The problem with ARM minisummits these days is it is very easy to
devolve into a nothing-but-dt meeting with a bunch of people sitting
around looking either annoyed or bored. We weren't able to pull enough
topics together when we tried to do an ARM minisummit at the ELC.

Instead of a traditional ARM minisummit, perhaps we should do an ARM
platforms minisprint instead. Light on any kind of presentations, but
have the right people in the room to try and knock out some of the
legacy backlog (which is kind of what Jason described)

g.

  parent reply	other threads:[~2014-05-15 12:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-11  3:00 Jason Cooper
2014-05-11 12:37 ` Jonathan Corbet
2014-05-11 13:59   ` Alexandre Belloni
2014-05-11 14:22   ` Olof Johansson
2014-05-15 12:15   ` Grant Likely [this message]
2014-05-15 13:38     ` Jason Cooper
2014-05-15 18:50     ` Rob Herring
2014-05-15 19:42       ` Jason Cooper
2014-05-16  3:30         ` Olof Johansson
2014-05-16  4:10           ` Jason Cooper
2014-05-16 18:31             ` Ben Hutchings
2014-05-16 18:42               ` Jason Cooper
2014-05-16 22:20                 ` Ben Hutchings
2014-05-19 12:20                   ` Arnd Bergmann
2014-05-19 22:41                     ` Peter Maydell
2014-05-19 23:06                     ` Rob Herring
2014-05-20  8:08                       ` Arnd Bergmann
2014-05-22 14:44                         ` Rob Herring
2014-05-23 13:48                         ` Linus Walleij
2014-05-23 14:42                           ` Arnd Bergmann
2014-05-23 13:46                       ` Linus Walleij
2014-05-23 13:40       ` Linus Walleij
2014-05-23 13:57         ` Arnd Bergmann
2014-05-16  3:39     ` Olof Johansson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140515121546.3A06AC40B0E@trevor.secretlab.ca \
    --to=grant.likely@secretlab.ca \
    --cc=corbet@lwn.net \
    --cc=jason@lakedaemon.net \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox