From: Chris Mason <clm@fb.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <dsterba@suse.cz>, Linus Torvalds <torvalds@linux-foundation.org>,
<linux-kernel@vger.kernel.org>, <linux-btrfs@vger.kernel.org>,
<stable@vger.kernel.org>
Subject: Re: [GIT PULL] Btrfs
Date: Tue, 4 Feb 2014 14:52:55 -0500 [thread overview]
Message-ID: <52F14517.5080102@fb.com> (raw)
In-Reply-To: <20140204195016.GA5264@kroah.com>
On 02/04/2014 02:50 PM, Greg KH wrote:
> On Mon, Feb 03, 2014 at 01:18:40PM -0500, Chris Mason wrote:
>> On Mon 03 Feb 2014 12:54:05 PM EST, David Sterba wrote:
>>> On Thu, Jan 30, 2014 at 04:52:54PM -0500, Chris Mason wrote:
>>>> Chris Mason (3) commits (+64/-32):
>>>> Btrfs: setup inode location during btrfs_init_inode_locked (+9/-9)
>>>> Btrfs: don't use ram_bytes for uncompressed inline items (+52/-22)
>>>
>>> The patches are CC: stable, but haven't gone through the mailinglist.
>>> Are they still going to be picked by stable?
>>
>> We do need both in -stable, I'll help with backports.
>
> Very few of the patches you marked for -stable, actually would apply (or
> build once applied.) Can you please send a set of patches you want
> applied?
Yes, I'll make a tree for you to pull. Between the acls and the block
layer changes, we had a lot of little things that will make it hard to
apply them directly, but the backports are pretty easy.
-chris
prev parent reply other threads:[~2014-02-04 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52EAC9B6.7090603@fb.com>
2014-02-03 17:54 ` [GIT PULL] Btrfs David Sterba
2014-02-03 18:18 ` Chris Mason
2014-02-04 19:50 ` Greg KH
2014-02-04 19:52 ` Chris Mason [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=52F14517.5080102@fb.com \
--to=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=gregkh@linuxfoundation.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).