From: Greg KH <greg@kroah.com>
To: David Howells <dhowells@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, keyrings@linux-nfs.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, Jeff Layton <jlayton@redhat.com>,
stable@kernel.org
Subject: Re: [PATCH] KEYS: Fix error handling in construct_key_and_link()
Date: Thu, 7 Jul 2011 16:11:26 -0700 [thread overview]
Message-ID: <20110707231126.GA5696@kroah.com> (raw)
In-Reply-To: <22918.1309435191@redhat.com>
On Thu, Jun 30, 2011 at 12:59:51PM +0100, David Howells wrote:
> Andrew Morton <akpm@linux-foundation.org> wrote:
>
> > So... this was a way to force 2.6.39.x users to upgrade to 3.0.x?
>
> Sorry, I always forget to cc stable.
I got it now, thanks.
prev parent reply other threads:[~2011-07-07 23:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 13:32 [PATCH] KEYS: Fix error handling in construct_key_and_link() David Howells
2011-06-29 22:36 ` Andrew Morton
2011-06-30 11:59 ` David Howells
2011-07-07 23:11 ` Greg KH [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=20110707231126.GA5696@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=jlayton@redhat.com \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=stable@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.