mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org,
	torvalds@osdl.org, davem@redhat.com
Subject: Re: Serial maintainership
Date: Thu, 8 Sep 2005 12:35:25 -0700	[thread overview]
Message-ID: <20050908123525.6bc0cb26.akpm@osdl.org> (raw)
In-Reply-To: <20050908172537.F5661@flint.arm.linux.org.uk>

Russell King <rmk+lkml@arm.linux.org.uk> wrote:
>
> 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.

Sometimes.  They're mistakes.

> 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.

The number of times I've been made aware of it happening is quite occasional.

> 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

Maintainer is (at least) cc'ed when the patch goes into -mm and when it
goes over to Linus.  Post-facto complaining is appreciated, so we can fix
the kernel and so I can tweak the process or the brain.

> - 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".

It shouldn't be necessary to complain more than once.  Sometimes I'll hang
on to a complained-about patch a) to remember that something needs to
happen and b) because an update is expected.  Once or twice I've
accidentally submitted such patches.

This particular patch ([SERIAL]: Avoid 'statement with no effect'
warnings.) didn't ever go into -mm.

  reply	other threads:[~2005-09-08 19:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-08 15:52 Russell King
2005-09-08 16:38 ` Alan Cox
2005-09-08 16:25   ` Russell King
2005-09-08 19:35     ` Andrew Morton [this message]
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=20050908123525.6bc0cb26.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    --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

all inboxes | Powered by JetHome®