From: Chris Mason <chris.mason@oracle.com>
To: Sage Weil <sage@newdream.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] missed btrfs fix
Date: Tue, 20 Sep 2011 17:00:21 -0400 [thread overview]
Message-ID: <1316551659-sup-7171@shiny> (raw)
Sage mentioned I was missing a patch. So I've retested and updated the
git tree. Since Linus did pull my tree yesterday, here's a new pull
request with the single commit.
Linus I have this in two flavors. One is merged on top of my for-linus
branch, which was 3.1-rc6 + my last pull request:
head: 0a7a0519d1789f3a222849421dbe91b6bddb88f5
git://github.com/chrismason/linux.git for-linus
Second is just against the btrfs-3.0 tree. I have the two branches just
so the N-1 world can update to the latest fixes without running the rest
of the rc kernel. I know in the git universe these are all the same,
but I'm assuming you'll want to skip my merge commit:
head: b6f3409b2197e8fcedb43e6600e37b7cfbe0715b
git://github.com/chrismason/linux.git btrfs-3.0
Sage Weil (1) commits (+6/-1):
Btrfs: reserve sufficient space for ioctl clone
fs/btrfs/ioctl.c | 7 ++++++-
1 files changed, 6 insertions(+), 1 deletions(-)
reply other threads:[~2011-09-20 21:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1316551659-sup-7171@shiny \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sage@newdream.net \
--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).