public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: James Bottomley <James.Bottomley@suse.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Stefani Seibold <stefani@seibold.net>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH] libsrp: fix compile failure
Date: Mon, 4 Jan 2010 13:35:55 -0800	[thread overview]
Message-ID: <20100104133555.d5231884.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.LNX.2.00.1001042206340.2277@pobox.suse.cz>

On Mon, 4 Jan 2010 22:12:26 +0100 (CET)
Jiri Kosina <jkosina@suse.cz> wrote:

> 
> [ added Stephen to CC ]
> 
> On Mon, 4 Jan 2010, James Bottomley wrote:
> 
> > Well, the fact that the compile failure wasn't detected before it went 
> > upstream should answer that ...
> > 
> > But to be more specific: linux-next is our integration tree (and also
> > the obscure architecture compile tree).  To ensure the best possible
> > integration, every tree should be built and tested in linux-next at
> > least once before it goes to Linus.  There were originally technical
> > reasons why -mm wasn't in ... I just thought they'd been fixed by now.
> 
> /me checks ...
> 
> Yes, it indeed is that way -- Andew pulls whole linux-next as one of the 
> patches into -mm series.
> 
> To make linux-next really working the way it is intended to work we need 
> to have -mm part of it, as it is used as a last point for a non-trivial 
> amount of patches before they enter Linus' tree.
> 
> Andrew, why do we have the current setup, and not the other way around?
> 

Because I suck.  I haven't yet got around to feeding -mm into
linux-next.  It's a bit tricky, because -mm is based on linux-next. 
Probably we'll address this by adding a "linux-next before the mm bits"
marker to linux-next.


  reply	other threads:[~2010-01-04 21:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-30 19:21 [PATCH] libsrp: fix compile failure James Bottomley
2009-12-30 19:33 ` Linus Torvalds
2009-12-30 19:55   ` James Bottomley
2010-01-04 15:21   ` Jiri Kosina
2010-01-04 17:22     ` James Bottomley
2010-01-04 17:35       ` Alan Cox
2010-01-04 19:24         ` Stefani Seibold
2010-01-04 19:37           ` James Bottomley
2010-01-04 22:36           ` Alan Cox
2010-01-04 21:12       ` Jiri Kosina
2010-01-04 21:35         ` Andrew Morton [this message]
2010-01-04 22:00           ` Jiri Kosina

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=20100104133555.d5231884.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=James.Bottomley@suse.de \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=stefani@seibold.net \
    --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