From: David Howells <dhowells@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: dhowells@redhat.com, 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, 30 Jun 2011 12:59:51 +0100 [thread overview]
Message-ID: <22918.1309435191@redhat.com> (raw)
In-Reply-To: <20110629153620.e00e9ef2.akpm@linux-foundation.org>
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.
David
next prev parent reply other threads:[~2011-06-30 12:00 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 [this message]
2011-07-07 23:11 ` Greg KH
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=22918.1309435191@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox