mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Greg KH <gregkh@suse.de>
Cc: tytso@mit.edu, torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCH] Fixes in the -stable tree, but not in mainline
Date: Tue, 18 Apr 2006 13:39:00 -0700	[thread overview]
Message-ID: <20060418133900.5e09cb23.akpm@osdl.org> (raw)
In-Reply-To: <20060418174205.GA684@suse.de>

Greg KH <gregkh@suse.de> wrote:
>
> On Tue, Apr 18, 2006 at 12:06:10PM -0400, Theodore Ts'o wrote:
> > On Mon, Apr 17, 2006 at 02:29:46PM -0700, Greg KH wrote:
> > > Here are 5 patches that are in the -stable tree, yet not currently fixed
> > > in your mainline tree.  One of them is a security fix, so it probably
> > > would be a good idea to get it into there :)
> > 
> > I thought one of the requirements for accepting a patch into -stable
> > was that it was already in mainline.  Was this a change in policy that
> > I missed, or just an oversight when we vetted these patches?
> > 
> > Not that I have anything against these patches, just curious in the
> > future if we should NACK patches proposed for -stable if we notice
> > that they aren't yet in mainline.
> 
> Sometimes some of these patches don't make it into Linus's tree because
> they get lost in the shuffle (like the Kconfig one), or because they
> were security issues that hit -stable first (like another one in there).
> 
> Either way, yes, the rule is that it should be in mainline, or in the
> pipe to get into mainline (as was the 5 in this patchset.)  I just
> wanted to make sure they made it into there, and didn't get lost.
> 

I had them queued up as well, but I'm being sluggish and Greg got there first.

      reply	other threads:[~2006-04-18 20:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-17 21:29 Greg KH
2006-04-17 21:33 ` [PATCH 1/5] isd200: limit to BLK_DEV_IDE Greg KH
2006-04-17 21:33   ` [PATCH 2/5] Fix block device symlink name Greg KH
2006-04-17 21:33     ` [PATCH 3/5] ext3: Fix missed mutex unlock Greg KH
2006-04-17 21:33       ` [PATCH 4/5] cciss: bug fix for crash when running hpacucli Greg KH
2006-04-17 21:33         ` [PATCH 5/5] shmat: stop mprotect from giving write permission to a readonly attachment (CVE-2006-1524) Greg KH
2006-04-18 16:06 ` [GIT PATCH] Fixes in the -stable tree, but not in mainline Theodore Ts'o
2006-04-18 17:42   ` Greg KH
2006-04-18 20:39     ` Andrew Morton [this message]

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=20060418133900.5e09cb23.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=tytso@mit.edu \
    /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®