All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Rob Herring <robh@kernel.org>,
	Jason Cooper <jason@lakedaemon.net>,
	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 15:59:30 +0200	[thread overview]
Message-ID: <20140511135930.GA334@piout.net> (raw)
In-Reply-To: <20140511083729.211e9b5f@lwn.net>

Hi,

On 11/05/2014 at 08:37:29 -0400, Jonathan Corbet 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 was supposed to take place at ELC, see:
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-April/245388.html

I'm not sure we should try to organize a new ARM mini summit so soon
after that failed attempt.

Regards,

-- 
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

WARNING: multiple messages have this Message-ID (diff)
From: alexandre.belloni@free-electrons.com (Alexandre Belloni)
To: linux-arm-kernel@lists.infradead.org
Subject: [Ksummit-discuss] [TECH TOPIC] ARM legacy board DT conversion finalization
Date: Sun, 11 May 2014 15:59:30 +0200	[thread overview]
Message-ID: <20140511135930.GA334@piout.net> (raw)
In-Reply-To: <20140511083729.211e9b5f@lwn.net>

Hi,

On 11/05/2014 at 08:37:29 -0400, Jonathan Corbet 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 was supposed to take place at ELC, see:
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-April/245388.html

I'm not sure we should try to organize a new ARM mini summit so soon
after that failed attempt.

Regards,

-- 
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-05-11 13:59 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-11  3:00 [Ksummit-discuss] [TECH TOPIC] ARM legacy board DT conversion finalization Jason Cooper
2014-05-11  3:00 ` Jason Cooper
2014-05-11 12:37 ` [Ksummit-discuss] " Jonathan Corbet
2014-05-11 12:37   ` Jonathan Corbet
2014-05-11 13:59   ` Alexandre Belloni [this message]
2014-05-11 13:59     ` Alexandre Belloni
2014-05-11 14:22   ` Olof Johansson
2014-05-11 14:22     ` Olof Johansson
2014-05-15 12:15   ` Grant Likely
2014-05-15 12:15     ` Grant Likely
2014-05-15 13:38     ` Jason Cooper
2014-05-15 13:38       ` Jason Cooper
2014-05-15 18:50     ` Rob Herring
2014-05-15 18:50       ` Rob Herring
2014-05-15 19:42       ` Jason Cooper
2014-05-15 19:42         ` Jason Cooper
2014-05-16  3:30         ` Olof Johansson
2014-05-16  3:30           ` Olof Johansson
2014-05-16  4:10           ` Jason Cooper
2014-05-16  4:10             ` Jason Cooper
2014-05-16 18:31             ` Ben Hutchings
2014-05-16 18:31               ` Ben Hutchings
2014-05-16 18:42               ` Jason Cooper
2014-05-16 18:42                 ` Jason Cooper
2014-05-16 22:20                 ` Ben Hutchings
2014-05-16 22:20                   ` Ben Hutchings
2014-05-19 12:20                   ` Arnd Bergmann
2014-05-19 12:20                     ` Arnd Bergmann
2014-05-19 22:41                     ` Peter Maydell
2014-05-19 22:41                       ` Peter Maydell
2014-05-19 23:06                     ` Rob Herring
2014-05-19 23:06                       ` Rob Herring
2014-05-20  8:08                       ` Arnd Bergmann
2014-05-20  8:08                         ` Arnd Bergmann
2014-05-22 14:44                         ` Rob Herring
2014-05-22 14:44                           ` Rob Herring
2014-05-23 13:48                         ` Linus Walleij
2014-05-23 13:48                           ` Linus Walleij
2014-05-23 14:42                           ` Arnd Bergmann
2014-05-23 14:42                             ` Arnd Bergmann
2014-05-23 13:46                       ` Linus Walleij
2014-05-23 13:46                         ` Linus Walleij
2014-05-23 13:40       ` Linus Walleij
2014-05-23 13:40         ` Linus Walleij
2014-05-23 13:57         ` Arnd Bergmann
2014-05-23 13:57           ` Arnd Bergmann
2014-05-16  3:39     ` Olof Johansson
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=20140511135930.GA334@piout.net \
    --to=alexandre.belloni@free-electrons.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.