From: Chris Mason <clm@fb.com>
To: <dsterba@suse.cz>
Cc: 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: Mon, 3 Feb 2014 13:18:40 -0500 [thread overview]
Message-ID: <52EFDD80.4050800@fb.com> (raw)
In-Reply-To: <20140203175405.GL1364@twin.jikos.cz>
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.
-chris
next prev parent reply other threads:[~2014-02-03 18:18 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 [this message]
2014-02-04 19:50 ` Greg KH
2014-02-04 19:52 ` Chris Mason
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=52EFDD80.4050800@fb.com \
--to=clm@fb.com \
--cc=dsterba@suse.cz \
--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).