From: Chris Mason <chris.mason@fusionio.com>
To: Filipe Brandenburger <filbranden@google.com>
Cc: Josef Bacik <JBacik@fusionio.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: LAST CALL FOR BTRFS-NEXT
Date: Thu, 21 Feb 2013 10:46:02 -0500 [thread overview]
Message-ID: <20130221154602.GE12051@shiny.masoncoding.com> (raw)
In-Reply-To: <CADU+-uBHcLUQQiv526xTheB_csCq5-fXOHgJbXCAZG9t5z2xdQ@mail.gmail.com>
On Thu, Feb 21, 2013 at 08:20:37AM -0700, Filipe Brandenburger wrote:
> Hi Josef,
>
> Please remove the following patch:
>
> Btrfs: move fs/btrfs/ioctl.h to include/uapi/linux/btrfs.h
> (55e301fd57a6239ec14b91a1cf2e70b3dd135194 in your btrfs-next.git)
>
> It's not fully cooked and I'm working on a second version of the patch
> that will do a little more rearranging of the header files according
> to the discussion on IRC a while ago.
>
Please send those as incremental fixes unless something is horribly
broken in the current patch.
-chris
next prev parent reply other threads:[~2013-02-21 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 14:26 LAST CALL FOR BTRFS-NEXT Josef Bacik
2013-02-20 14:42 ` Liu Bo
2013-02-20 15:12 ` David Sterba
2013-02-20 15:35 ` Alex Lyakas
2013-02-20 15:39 ` Chris Mason
2013-02-21 15:20 ` Filipe Brandenburger
2013-02-21 15:46 ` Chris Mason [this message]
2013-02-21 17:55 ` Filipe Brandenburger
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=20130221154602.GE12051@shiny.masoncoding.com \
--to=chris.mason@fusionio.com \
--cc=JBacik@fusionio.com \
--cc=filbranden@google.com \
--cc=linux-btrfs@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