From: Greg KH <gregkh@linuxfoundation.org>
To: Alexander Block <ablock84@googlemail.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] Btrfs: merge inode_list in __merge_refs
Date: Fri, 9 Nov 2012 08:01:29 +0100 [thread overview]
Message-ID: <20121109070129.GA1199@kroah.com> (raw)
In-Reply-To: <CAB9VWqAJZCr5HiHwpisiuKNq0Rarba9YL9SfxudssR9YcQ75sA@mail.gmail.com>
On Thu, Nov 08, 2012 at 10:35:19PM +0100, Alexander Block wrote:
>
> Used wrong CC for stable list. Corrected now.
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read Documentation/stable_kernel_rules.txt
for how to do this properly.
</formletter>
prev parent reply other threads:[~2012-11-09 7:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 21:27 [PATCH] Btrfs: merge inode_list in __merge_refs Alexander Block
2012-11-08 21:35 ` Alexander Block
2012-11-09 7:01 ` 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=20121109070129.GA1199@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ablock84@googlemail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).