From: Greg KH <greg@kroah.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: ksummit-2012-discuss@lists.linux-foundation.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Ksummit-2012-discuss] [ATTEND or not ATTEND] That's the question!
Date: Fri, 15 Jun 2012 16:34:13 -0700 [thread overview]
Message-ID: <20120615233413.GB8894@kroah.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1206152313310.3086@ionos>
On Sat, Jun 16, 2012 at 12:56:36AM +0200, Thomas Gleixner wrote:
> So the main questions I want to raise on Kernel Summit are:
>
> - How do we cope with the need to review the increasing amount of
> (insane) patches and their potential integration?
That's a very good question, and I've been wondering if someone is
trying to flood us with crap submissions just to try to DoS us and slow
us down. If not, it's an interesting "attack" vector onto our
development process that we need to be able to handle better.
> - How do we prevent further insanity to known problem spaces (like
> cpu hotplug) without stopping progress?
Progress can slow, if we want it to, in some areas, just to let people
get the time to fix up the issues we currently have. That saves time in
the long run, but requires that someone make it very clear as to what is
going on and how it will change in the future.
But, both of these are great things to talk about, I like it.
> A side question, but definitely related is:
>
> - How do we handle "established maintainers" who are mainly
> interested in their own personal agenda and ignoring justified
> criticism just because they can?
The wonderful, "how do we remove a maintainer who isn't working out"
problem. It's a tough one, I don't think we really have any standard
way. Luckily in the past, the insane ones went away on their own :)
greg k-h
next prev parent reply other threads:[~2012-06-15 23:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 22:56 Thomas Gleixner
2012-06-15 23:34 ` Greg KH [this message]
2012-06-16 10:50 ` [Ksummit-2012-discuss] " Thomas Gleixner
2012-06-16 13:29 ` Jonathan Corbet
2012-06-16 13:32 ` Frederic Weisbecker
2012-06-16 13:56 ` Rafael J. Wysocki
2012-06-17 10:40 ` Thomas Gleixner
2012-06-17 18:51 ` Greg KH
2012-06-17 18:58 ` Mark Brown
2012-06-20 19:51 ` J. Bruce Fields
2012-07-06 9:43 ` Glauber Costa
2012-07-06 9:54 ` Frederic Weisbecker
2012-07-06 9:59 ` Glauber Costa
2012-07-06 10:00 ` Srivatsa S. Bhat
2012-07-06 10:03 ` Glauber Costa
2012-07-06 10:21 ` Srivatsa S. Bhat
2012-07-06 10:11 ` Richard Cochran
2012-07-06 10:14 ` Glauber Costa
2012-07-06 10:36 ` Srivatsa S. Bhat
2012-07-06 10:43 ` Glauber Costa
2012-07-06 12:42 ` Steven Rostedt
2012-07-17 22:17 ` david
2012-06-16 11:30 ` Alan Cox
2012-06-16 15:03 ` Phil Turmel
2012-06-16 16:43 ` Myklebust, Trond
2012-06-20 0:40 ` Dave Chinner
2012-06-17 17:04 ` Mark Brown
2012-06-19 15:45 ` Bjorn Helgaas
2012-06-19 19:18 ` Roland Dreier
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=20120615233413.GB8894@kroah.com \
--to=greg@kroah.com \
--cc=ksummit-2012-discuss@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®