From: Greg KH <greg@kroah.com>
To: James Morris <jmorris@namei.org>
Cc: David Howells <dhowells@redhat.com>,
keyrings@linux-nfs.org, Dan Carpenter <error27@gmail.com>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, torvalds@osdl.org,
Oleg Nesterov <oleg@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
stable@kernel.org
Subject: Re: [stable] [PATCH] KEYS: Return more accurate error codes
Date: Mon, 24 May 2010 14:43:56 -0700 [thread overview]
Message-ID: <20100524214356.GH16655@kroah.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1005180851180.21768@tundra.namei.org>
On Tue, May 18, 2010 at 08:51:43AM +1000, James Morris wrote:
> On Mon, 17 May 2010, David Howells wrote:
>
> > From: Dan Carpenter <error27@gmail.com>
> >
> > We were using the wrong variable here so the error codes weren't being returned
> > properly. The original code returns -ENOKEY.
> >
> > Signed-off-by: Dan Carpenter <error27@gmail.com>
> > Signed-off-by: David Howells <dhowells@redhat.com>
>
> Queued for Linus -- is also likely a -stable candidate.
If so, please just put a:
Cc: stable <stable@kernel.org>
to the signed-off-by area of the patch. That way I automatically get
notified when it goes into Linus's tree, and I don't have to go dig and
try to match up a random email reference like this one with the actual
patch in Linus's tree...
thanks,
greg k-h
prev parent reply other threads:[~2010-05-24 22:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 13:42 [PATCH] KEYS: Return more accurate error codes David Howells
2010-05-17 22:51 ` James Morris
2010-05-24 21:43 ` 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=20100524214356.GH16655@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=error27@gmail.com \
--cc=jmorris@namei.org \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=stable@kernel.org \
--cc=torvalds@osdl.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