From: Greg KH <greg@kroah.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: ksummit-2008-discuss@lists.linux-foundation.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Ksummit-2008-discuss] Current List of Kernel Summit suggested topics from the discuss list
Date: Thu, 3 Jul 2008 11:27:07 -0700 [thread overview]
Message-ID: <20080703182707.GA12215@kroah.com> (raw)
In-Reply-To: <1214577710.3394.14.camel@localhost.localdomain>
On Fri, Jun 27, 2008 at 09:41:49AM -0500, James Bottomley wrote:
> Hi All,
>
> This is the synopsis of the currently suggested topics so far. That's
> not to say this is the list we will be doing, just to say that if
> there's something you think we should be discussing and it's not on the
> list, now would be a good time to add it (don't trust the programme
> committee magically to add it at the last minute ...)
Another proposal:
Working well with other subsystems - Jean Delvare
There are a number of times where different subsystems in the
kernel need to interact with each other in ways that are not
always easy or obvious. This talk will be about some examples
of how this has been done well, as well as work to figure out
how to handle this better in the future.
thanks,
greg k-h
next prev parent reply other threads:[~2008-07-03 18:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 14:41 Current List of Kernel Summit suggested topics from the discuss list James Bottomley
2008-06-27 14:53 ` [Ksummit-2008-discuss] " Arjan van de Ven
2008-06-27 15:09 ` James Bottomley
2008-06-27 15:19 ` Rafael J. Wysocki
2008-06-27 17:35 ` Jesse Barnes
2008-06-27 18:11 ` H. Peter Anvin
2008-06-27 18:23 ` Jesse Barnes
2008-06-27 15:19 ` Christoph Hellwig
2008-06-27 17:18 ` Jens Axboe
2008-07-03 9:29 ` Arnd Bergmann
2008-07-03 18:27 ` Greg KH [this message]
2008-07-03 23:59 ` [Ksummit-2008-discuss] " Stephen Rothwell
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=20080703182707.GA12215@kroah.com \
--to=greg@kroah.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=ksummit-2008-discuss@lists.linux-foundation.org \
--cc=linux-kernel@vger.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