mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Prarit Bhargava <prarit@redhat.com>,
	drjones@redhat.com, suresh.b.siddha@intel.com, x86@kernel.org,
	linux-kernel@vger.kernel.org, clalance@redhat.com,
	stable@kernel.org
Subject: Re: [stable] [PATCH] Fix NULL pointer for Xen guests
Date: Wed, 28 Apr 2010 12:15:02 -0700	[thread overview]
Message-ID: <20100428191502.GA29921@kroah.com> (raw)
In-Reply-To: <20100428115039.c276594a.akpm@linux-foundation.org>

On Wed, Apr 28, 2010 at 11:50:39AM -0700, Andrew Morton wrote:
> I worry that if the -stable maintainer see me drop a patch, but the
> patch in Linus's tree doesn't have the stable tag, they might not merge
> the fix into -stable.  I bugged them about this scenario recently and
> the reply was a bit waffly ;)

It was?

I try my best, that if I see you drop a patch, to go dig through Linus's
tree to find if it landed there.  If not, I leave it in my queue, and do
that for a few releases.  If after a long time (like 6 months) I either
ping someone, or just drop it from my queue as I guessed that someone
dropped it for some reason.

If I miss one of these, please let me know.

> By far the safest thing to do is to include the stable tag in your
> changelog right at the outset.

Yes, that's the _easiest_ and will not get lost.

thanks,

greg k-h

  reply	other threads:[~2010-04-28 19:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-27 15:24 Prarit Bhargava
2010-04-27 16:58 ` [LKML] " Konrad Rzeszutek Wilk
2010-04-27 17:09   ` Prarit Bhargava
2010-04-27 17:59     ` Andrew Jones
2010-04-27 18:34     ` Konrad Rzeszutek Wilk
2010-04-27 18:47       ` Prarit Bhargava
2010-05-03 19:16         ` Konrad Rzeszutek Wilk
2010-05-03 19:56           ` Prarit Bhargava
2010-05-04 15:02           ` [LKML] " Konrad Rzeszutek Wilk
2010-05-04 15:21             ` Prarit Bhargava
2010-04-28 18:26 ` Andrew Morton
2010-04-28 18:29   ` Prarit Bhargava
2010-04-28 18:42     ` Suresh Siddha
2010-04-28 18:50     ` Andrew Morton
2010-04-28 19:15       ` Greg KH [this message]
2010-04-30 20:55 ` H. Peter Anvin
2010-04-30 21:33   ` H. Peter Anvin
2010-04-30 22:01   ` Prarit Bhargava
2010-04-30 21:36 ` [tip:x86/urgent] x86: Fix NULL pointer access in irq_force_complete_move() " tip-bot for Prarit Bhargava
2010-05-04 15:02   ` [LKML] " Konrad Rzeszutek Wilk

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=20100428191502.GA29921@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=clalance@redhat.com \
    --cc=drjones@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prarit@redhat.com \
    --cc=stable@kernel.org \
    --cc=suresh.b.siddha@intel.com \
    --cc=x86@kernel.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

Powered by JetHome