All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	David Miller <davem@davemloft.net>,
	torvalds@linux-foundation.org, linville@tuxdriver.com,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: Please consider reverting 7d930bc33653d5592dc386a76a38f39c2e962344
Date: Tue, 3 Nov 2009 22:34:33 -0800	[thread overview]
Message-ID: <20091103223433.23765578.akpm@linux-foundation.org> (raw)
In-Reply-To: <1257234299.28469.25.camel@johannes.local>

On Tue, 03 Nov 2009 08:44:59 +0100 Johannes Berg <johannes@sipsolutions.net> wrote:

> On Tue, 2009-11-03 at 16:16 +0900, Marcel Holtmann wrote:
> 
> > and can we please stop jumping the gun here and going past the subsystem
> > maintainers. I think this happens a little bit too much lately.
> 
> I'll rant a bit too -- I've been very annoyed by this many times.

Problem is, subsystem maintainers are very unreliable.

Right now I'm sitting on 17 patches which I think should be in 2.6.32,
which I need to plead with subsystem maintainers to take a look at. 
They've already seen the patches (usually at least twice) and they've
just blown them off.  This is typical.

And then there are the 100 to 200 non-critical patches which I'm always
sitting on, similarly ignored.  And I'm increasingly just ignoring
stuff nowadays because this situation is so bad.

And then there are all the bug reports which flow in one ear and out
the other.

Now, some subsystem maintainer are good, and some aren't.  I'm probably
the only person who could write the detailed list for each column. 
Unfortunately, people who have better lives than me are best off
assuming that a subsystem maintainer is unreliable.  If the problem is
severe enough, bypassing the maintainer is a sensible default.


  parent reply	other threads:[~2009-11-04  6:35 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03  5:31 Please consider reverting 7d930bc33653d5592dc386a76a38f39c2e962344 Dmitry Torokhov
2009-11-03  6:49 ` David Miller
2009-11-03  6:52   ` Dmitry Torokhov
2009-11-03  7:16     ` Marcel Holtmann
2009-11-03  7:44       ` Johannes Berg
2009-11-03  8:22         ` Dmitry Torokhov
2009-11-03  8:31           ` Johannes Berg
2009-11-03  8:47             ` Dmitry Torokhov
2009-11-03  8:57               ` Johannes Berg
2009-11-03 15:29                 ` Marcel Holtmann
2009-11-03 15:38                   ` Linus Torvalds
2009-11-05 19:19                   ` Pavel Machek
2009-11-03 15:31         ` Linus Torvalds
2009-11-04  6:34         ` Andrew Morton [this message]
2009-11-04  8:41           ` David Miller
2009-11-04 15:23             ` Andrew Morton
2009-11-04 16:32               ` David Miller
2009-11-03 15:26       ` Linus Torvalds
2009-11-03 15:36         ` Marcel Holtmann
2009-11-03 15:43           ` Linus Torvalds
2009-11-03 16:07             ` Linus Torvalds
2009-11-03 16:08             ` Marcel Holtmann
2009-11-03 16:23               ` Linus Torvalds
2009-11-03 16:37                 ` Linus Torvalds
2009-11-03 16:44                 ` Marcel Holtmann
2009-11-03 16:59                   ` Linus Torvalds
2009-11-03 16:29               ` Ingo Molnar
2009-11-03 16:49                 ` Marcel Holtmann
2009-11-03 17:04                   ` Ingo Molnar
2009-11-03 17:24                 ` Luis R. Rodriguez
2009-11-03 17:37                   ` Linus Torvalds
2009-11-03 17:49                     ` Dmitry Torokhov
2009-11-03 17:55                     ` Luis R. Rodriguez
2009-11-03 15:54           ` Zdenek Kabelac

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=20091103223433.23765578.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=marcel@holtmann.org \
    --cc=torvalds@linux-foundation.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.