public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: David Miller <davem@davemloft.net>
Cc: sfr@canb.auug.org.au, mingo@elte.hu, andi@lisas.de,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	mchehab@infradead.org
Subject: Re: Linux 2.6.26-rc1
Date: Mon, 5 May 2008 17:16:57 -0700	[thread overview]
Message-ID: <20080505171657.64386de7.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080505.165501.62584352.davem@davemloft.net>

On Mon, 05 May 2008 16:55:01 -0700 (PDT) David Miller <davem@davemloft.net> wrote:

> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Tue, 6 May 2008 09:51:22 +1000
> 
> > I (and I assume Andrew) have been carrying them since then but noone took
> > them up.  I guess (as Andrew pointed out to me) I should have pushed them.
> 
> So what should I do now?
>
> I have Ingo's IRDA PNP fixes in my net-2.6 tree and that's already
> publicly visible, so I'd need to add revert changesets if people want
> me to remove it.

Uncharted territory here.

As we discussed last week, I won't carry these patches because they're
already upstream.  It turns out that "upstream" in this case is linux-next
itself, which is an unexpected place for patches to be mastered.

So I suggest that Stephen send patches such as this into Linus sooner
rather than later.  Because nobody else will.

Well.  They _might_.  In this case Len could merge the patch in which case
Stephen would drop it and the fix would dawdle around in the acpi tree for
a while.

Ho hum, hopefully this isn't a common case.  Often Linus or I will just do
a maintainer bypass on things like this, but my ability to do that is now
much reduced because a) I can't merge the patch and b) when I _do_ try to
do that, it's "huh, we already fixed it".

So... I hereby appoint Stephen random-build-fix-monkey.

  reply	other threads:[~2008-05-06  0:18 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8287f540805041818g534c4e02qaadb0e749c5f3439@mail.gmail.com>
2008-05-03 19:38 ` Linux 2.6.26-rc1 Linus Torvalds
2008-05-03 21:47   ` Alistair John Strachan
2008-05-03 21:53     ` Alistair John Strachan
2008-05-04 12:30       ` Robin Holt
2008-05-04 13:56         ` Alistair John Strachan
2008-05-04 16:09           ` Robin Holt
2008-05-04 16:33             ` Alistair John Strachan
2008-05-05 21:04             ` Mauro Carvalho Chehab
2008-05-06  8:02               ` Alistair John Strachan
2008-05-06 10:31                 ` Mauro Carvalho Chehab
2008-05-06 14:34                   ` Stefan Richter
2008-05-06 14:54                     ` Stefan Richter
2008-05-06 19:13                     ` Mauro Carvalho Chehab
2008-05-06 19:44                       ` Stefan Richter
2008-05-06 20:06                         ` Mauro Carvalho Chehab
2008-05-06 20:47                           ` Stefan Richter
2008-05-06 22:39                             ` Mauro Carvalho Chehab
2008-05-06 23:36                               ` Stefan Richter
2008-05-08 12:48                                 ` Mauro Carvalho Chehab
2008-05-08 14:11                                   ` Stefan Richter
2008-05-06 23:48                             ` Stefan Richter
2008-05-04  7:29   ` [patch] sysfs: build fix Ingo Molnar
2008-05-04 18:40   ` Linux 2.6.26-rc1 Jan Engelhardt
2008-05-05  5:39   ` Andreas Mohr
2008-05-05  7:30     ` Ingo Molnar
2008-05-05 20:14       ` Mauro Carvalho Chehab
2008-05-06 13:07         ` Ingo Molnar
2008-05-07  8:35           ` Ingo Molnar
2008-05-05 23:51       ` Stephen Rothwell
2008-05-05 23:55         ` David Miller
2008-05-06  0:16           ` Andrew Morton [this message]
2008-05-06  5:57             ` Stephen Rothwell
2008-05-06  0:21           ` Ingo Molnar
2008-05-06  5:35           ` Stephen Rothwell
2008-05-06  6:56             ` David Miller
2008-05-06  7:26               ` Stephen Rothwell
2008-05-06  0:17         ` Ingo Molnar
2008-05-06  5:48           ` Stephen Rothwell
2008-05-06  6:07   ` Scheduling problems ? [ Was: Linux 2.6.26-rc1 ] J.A. Magallón
2008-05-06 13:11     ` Ingo Molnar

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=20080505171657.64386de7.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=andi@lisas.de \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=mingo@elte.hu \
    --cc=sfr@canb.auug.org.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox