Ok,
Nothing terribly broken with it, I can do with incremental commits on
top of it, thanks!
Filipe
On Thu, Feb 21, 2013 at 7:46 AM, Chris Mason wrote:
> On Thu, Feb 21, 2013 at 08:20:37AM -0700, Filipe Brandenburger wrote:
>> Hi Josef,
>>
>> Please remove the following patch:
>>
>> Btrfs: mov
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
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 fi
On Wed, Feb 20, 2013 at 08:35:30AM -0700, Alex Lyakas wrote:
> Hi Josef,
> can you please consider including these two patches from Jan 28:
> https://patchwork.kernel.org/patch/2057051/
> https://patchwork.kernel.org/patch/2057071/
>
> I realize they have "V2" label, although the cover letter had
Hi Josef,
can you please consider including these two patches from Jan 28:
https://patchwork.kernel.org/patch/2057051/
https://patchwork.kernel.org/patch/2057071/
I realize they have "V2" label, although the cover letter had "V3",
this was my bad. However, they both apply to what you have now in
b
Please add this patch to next queue
btrfs: limit fallocate extent reservation to 256MB
https://patchwork.kernel.org/patch/1752311/
Tested-by: David Sterba
thanks,
david
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.or
On Wed, Feb 20, 2013 at 09:26:12AM -0500, Josef Bacik wrote:
> Hello,
>
> If you have patches in btrfs-next, make sure they are the right ones so we
> don't
> have to rebase and repull and merge and all that crap for this merge window.
> If
> I'm missing stuff that's fine, I can throw that on t
Hello,
If you have patches in btrfs-next, make sure they are the right ones so we don't
have to rebase and repull and merge and all that crap for this merge window. If
I'm missing stuff that's fine, I can throw that on top, but you need to make
sure I have the right versions of stuff already in t
