ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Rob Herring <robh@kernel.org>,
	Jason Cooper <jason@lakedaemon.net>,
	"ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>,
	Linux ARM Kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] ARM legacy board DT conversion finalization
Date: Sun, 11 May 2014 07:22:36 -0700	[thread overview]
Message-ID: <CAOesGMjY7dwSt3Cc582qy1DHi9qFsY6rUcvU4+YNWya7AyK=fQ@mail.gmail.com> (raw)
In-Reply-To: <20140511083729.211e9b5f@lwn.net>

On Sun, May 11, 2014 at 5:37 AM, 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;

Agreed.

> hopefully one of those is in the works?

Not this year.

Last year we had a two-day workshop, and most of it ended up centered
around DT. This year, that topic has overlap with other architectures
so it's likely better handled as shared technical track topic.

There doesn't seem to be a whole lot of topics needing to be covered,
at least not based on the call for proposals at ELC (see reply from
Alexandre). So, we'll take a break this year and come back and
organize one next year if there's more material again.

I suppose it's a positive sign; things are running relatively smoothly
right now so there's less stuff to iron out in person, or at least to
iron out together with a roomful of attendees.


-Olof

  parent reply	other threads:[~2014-05-11 14:22 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 [this message]
2014-05-15 12:15   ` Grant Likely
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='CAOesGMjY7dwSt3Cc582qy1DHi9qFsY6rUcvU4+YNWya7AyK=fQ@mail.gmail.com' \
    --to=olof@lixom.net \
    --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