public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@osdl.org>,
	Dave Miller <davem@redhat.com>, Andrew Morton <akpm@osdl.org>
Subject: Re: Serial maintainership
Date: Thu, 8 Sep 2005 17:25:37 +0100	[thread overview]
Message-ID: <20050908172537.F5661@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1126197523.19834.49.camel@localhost.localdomain>; from alan@lxorguk.ukuu.org.uk on Thu, Sep 08, 2005 at 05:38:43PM +0100

On Thu, Sep 08, 2005 at 05:38:43PM +0100, Alan Cox wrote:
> On Iau, 2005-09-08 at 16:52 +0100, Russell King wrote:
> > I notice DaveM's taken over serial maintainership.  Please arrange for
> > serial patches to be sent to davem in future, thanks.  (All ARM serial
> > drivers are broken as of Tuesday.)
> > 
> > I might take a different view if I at least had a curtious CC: of the
> > patch, which I had already asked akpm to reject.
> > 
> > Thanks.  That's another subsystem I don't have to care about anymore.
> 
> Please remember to send Linus a patch updating MAINTAINERS if so.

Well, it appears that we're fast approaching meltdown in kernel
land - patches are being applied despite maintainers objection,
maintainers are not being copied with changes in their area, etc.

I might mind less with the occasional slip up if it was occasional,
but it doesn't appear to be anymore - maybe not from my perspective.

This morning Andi Kleen stated:

 "normally he (akpm) asks you before finally sending them off -
  then you can complain again"

I don't appear to be asked by akpm - patches from -mm are sent
to Linus CC'd me, and that occurs during the night.  Come the
morning, they're in Linus tree so unless one is awake reading
email 24 hours a day, it's impossible to "complain again".

Is there a concerted effort to maintainers?  It certainly seems
so from my perspective.

---
Paranoia, n.
   1. A psychotic disorder characterized by delusions of persecution
      with or without grandeur, often strenuously defended with apparent
      logic and reason.
   2. Extreme, irrational distrust of others.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2005-09-08 16:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-08 15:52 Serial maintainership Russell King
2005-09-08 16:38 ` Alan Cox
2005-09-08 16:25   ` Russell King [this message]
2005-09-08 19:35     ` Andrew Morton
2005-09-08 16:27   ` Linus Torvalds
2005-09-08 20:13     ` David S. Miller
2005-09-08 20:22       ` Russell King
2005-09-08 20:26         ` David S. Miller
2005-09-08 20:39           ` Linus Torvalds
2005-09-08 20:42             ` David S. Miller
2005-09-08 21:22               ` Linus Torvalds
2005-09-08 21:26                 ` David S. Miller
2005-09-08 21:31                 ` Russell King
2005-09-08 21:37                 ` Linus Torvalds
2005-09-08 20:31       ` viro

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=20050908172537.F5661@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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