linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [Ksummit-2012-discuss] ARM mini-summit
Date: Wed, 11 Jul 2012 14:35:32 +0200	[thread overview]
Message-ID: <de55bfacdc06182dd4f3a36722fcc9fe@localhost> (raw)
In-Reply-To: <20120711115755.GF22437@arm.com>

On Wed, 11 Jul 2012 12:57:55 +0100, Catalin Marinas
<catalin.marinas@arm.com> wrote:
> On Wed, Jul 11, 2012 at 12:28:29PM +0100, Arnd Bergmann wrote:
>> On Wednesday 11 July 2012, James Bottomley wrote:
>> > Hi All,
>> > 
>> > We have set aside the second day of the kernel summit (Tuesday 28
>> > August) as mini-summit day.  So far we have only the PCI mini summit
on
>> > this day, so if you can think of other topics, please send them to
the
>> > kernel summit discuss list:
>> > 
>> > ksummit-2012-discuss at lists.linux-foundation.org
>> > 
>> > Looking at the available rooms, we think we can run about four or
five
>> > mini summits.
>> > 
>> > As an added incentive, mini summit organisers get to pick who they
>> > invite and all the people they pick will get an automatic invitation
to
>> > the third day of the kernel summit (but not the core first day) and
the
>> > evening events.
>> 
>> There is a lot of interest in having another ARM mini-summit, as we had
>> last
>> year. Previously, Grant Likely organized this with Olof and me, but
>> right now
>> Grant is in an extended offline period and Olof is currently on
vacation
>> as well. Will Deacon already contacted me and he is interested in
helping
>> out with organizing the mini-summit, so the two of us could be the
>> primary
>> contacts, with Grant and Olof joining in as time permits.
>> 
>> I'm planning to send out an initial email to potential participants
today
>> or tomorrow to get an idea of who would be joining.
> 
> I'm definitely interested in attending this.

Same here. The previous incarnation of the mini-summit was very
successful, and I would be very interested in attending another one.

It's not like we're having any shortage of things to discuss these days...
;-)

Thanks,

        M.
-- 
Fast, cheap, reliable. Pick two.

  reply	other threads:[~2012-07-11 12:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1341994155.3522.16.camel@dabdike.int.hansenpartnership.com>
2012-07-11 11:28 ` ARM mini-summit Arnd Bergmann
2012-07-11 11:57   ` [Ksummit-2012-discuss] " Catalin Marinas
2012-07-11 12:35     ` Marc Zyngier [this message]
2012-07-12 22:08       ` Kukjin Kim
2012-07-13  7:18         ` Tony Lindgren
2012-07-27 13:57           ` Igor Grinberg
2012-07-11 12:15   ` Grant Likely
2012-07-11 14:05     ` [Ksummit-2012-discuss] " Konrad Rzeszutek Wilk
2012-07-11 19:27       ` Konrad Rzeszutek Wilk
2012-07-11 20:06         ` Arnd Bergmann
2012-07-11 20:11           ` Konrad Rzeszutek Wilk
2012-07-11 21:16           ` Marc Zyngier
2012-07-11 21:58             ` Rob Herring
2012-07-12 13:58             ` Stefano Stabellini
2012-07-12 13:31         ` Stefano Stabellini
2012-07-11 21:02   ` David Brown
2012-07-13  2:33   ` 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=de55bfacdc06182dd4f3a36722fcc9fe@localhost \
    --to=marc.zyngier@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).