From: Ben Hutchings <bhutchings@solarflare.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
<ksummit-2012-discuss@lists.linux-foundation.org>,
<netdev@vger.kernel.org>
Subject: Re: [Ksummit-2012-discuss] Organising Mini Summits within the Kernel Summit
Date: Fri, 13 Jul 2012 23:35:31 +0100 [thread overview]
Message-ID: <1342218931.2965.30.camel@bwh-desktop.uk.solarflarecom.com> (raw)
In-Reply-To: <20120711084417.4a8132ff@nehalam.linuxnetplumber.net>
On Wed, 2012-07-11 at 08:44 -0700, Stephen Hemminger wrote:
> On Wed, 11 Jul 2012 09:09:15 +0100
> James Bottomley <James.Bottomley@HansenPartnership.com> 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@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.
> >
> > James
>
> Is there enough interest to have a networking mini-summit?
I would be interested.
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
prev parent reply other threads:[~2012-07-13 22:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1341994155.3522.16.camel@dabdike.int.hansenpartnership.com>
2012-07-11 15:44 ` [Ksummit-2012-discuss] Organising Mini Summits within the Kernel Summit Stephen Hemminger
2012-07-13 22:35 ` Ben Hutchings [this message]
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=1342218931.2965.30.camel@bwh-desktop.uk.solarflarecom.com \
--to=bhutchings@solarflare.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=ksummit-2012-discuss@lists.linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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