From: Greg KH <gregkh@linuxfoundation.org>
To: Herton Ronaldo Krzesinski <herton.krzesinski@canonical.com>
Cc: Tyler Hicks <tyhicks@canonical.com>,
John Johansen <john.johansen@canonical.com>,
Colin Ian King <colin.king@canonical.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
kernel-team@lists.ubuntu.com
Subject: Re: [ 3.5.yuz extended stable] Patch "eCryptfs: Unlink lower inode when ecryptfs_create() fails" has been added to staging queue
Date: Mon, 12 Nov 2012 15:09:15 -0800 [thread overview]
Message-ID: <20121112230915.GB4040@kroah.com> (raw)
In-Reply-To: <1352755737-16123-1-git-send-email-herton.krzesinski@canonical.com>
On Mon, Nov 12, 2012 at 07:28:57PM -0200, Herton Ronaldo Krzesinski wrote:
> This is a note to let you know that I have just added a patch titled
>
> eCryptfs: Unlink lower inode when ecryptfs_create() fails
>
> to the linux-3.5.y-queue branch of the 3.5.yuz extended stable tree
> which can be found at:
>
> http://kernel.ubuntu.com/git?p=ubuntu/linux.git;a=shortlog;h=refs/heads/linux-3.5.y-queue
>
> If you, or anyone else, feels it should not be added to the 3.5
> Linux kernel, or for any feedback related to it, please reply to
> this email. For more information on extended stable, see
> https://wiki.ubuntu.com/Kernel/Dev/ExtendedStable
It's nice that you are doing this work, but please don't send these
types of messages to the stable@vger.kernel.org mailing list as they
aren't really relevant there at all. I doubt that lkml also cares about
them either, I know I always strip off public mailing lists (except for
stable) when sending these types of messages.
Also, you might want to reword that last paragraph a bit...
thnaks,
greg k-h
prev parent reply other threads:[~2012-11-12 23:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 21:28 Herton Ronaldo Krzesinski
2012-11-12 23:09 ` 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=20121112230915.GB4040@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=colin.king@canonical.com \
--cc=herton.krzesinski@canonical.com \
--cc=john.johansen@canonical.com \
--cc=kernel-team@lists.ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tyhicks@canonical.com \
/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®