From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Arjan van de Ven <arjan@linux.intel.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: Fri, 27 Jun 2008 10:09:16 -0500 [thread overview]
Message-ID: <1214579356.3394.25.camel@localhost.localdomain> (raw)
In-Reply-To: <4864FEFB.2050405@linux.intel.com>
On Fri, 2008-06-27 at 07:53 -0700, Arjan van de Ven wrote:
> 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 ...)
> >
> > James
> >
>
> I'd like to propose a topic about kernel quality; there's been a lot of
> lkml traffic about it (in ups and downs). As part of this topic I could present
> trends, data and conclusions from the kerneloops.org project. I'm sure Andrew has
> a set of data and views from his part of the world, and the regressions topic
> could fall under this too. If we, unlike last year, ask various subsystem maintainers
> to prepare data or at least something more solid than "eh I think we're fine" ahead of the
> conference, we could have a more thought out set of inputs from that direction as well.
Really, then you want this topic:
> 5. Tracking Regressions - Rafael Wysocki
> * Describe experiences with the current running of the
> regression lists
> * How could we make the current list and practice more
> useful
broadened to include all quality issues?
James
next prev parent reply other threads:[~2008-06-27 15:09 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 [this message]
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 ` [Ksummit-2008-discuss] " Greg KH
2008-07-03 23:59 ` 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=1214579356.3394.25.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=arjan@linux.intel.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 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.