From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: "Robert Święcki" <robert@swiecki.net>,
"David Howells" <dhowells@redhat.com>,
lkml <linux-kernel@vger.kernel.org>,
stable@kernel.org
Subject: Re: [PATCH] Set cred->user_ns in key_replace_session_keyring
Date: Thu, 26 May 2011 13:40:45 -0700 [thread overview]
Message-ID: <BANLkTikjL9znUnsAKhJfThEMtJ2aevAF-A@mail.gmail.com> (raw)
In-Reply-To: <20110526203819.GA27529@mail.hallyn.com>
On Thu, May 26, 2011 at 1:38 PM, Serge E. Hallyn <serge@hallyn.com> wrote:
>
> Stable/whoever, should I re-send this patch separately, or does this suffice?
I'll add the Cc and update the description to point to the commit it
was introduced in, and it will all be fine. Then the stable team will
get it automatically when I push out.
Linus
next prev parent reply other threads:[~2011-05-26 20:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 20:25 Serge E. Hallyn
2011-05-26 20:31 ` Linus Torvalds
2011-05-26 20:38 ` Serge E. Hallyn
2011-05-26 20:40 ` Linus Torvalds [this message]
2011-05-27 0:04 ` Serge E. Hallyn
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=BANLkTikjL9znUnsAKhJfThEMtJ2aevAF-A@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robert@swiecki.net \
--cc=serge@hallyn.com \
--cc=stable@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
all inboxes | Powered by JetHome®