From: Li Zefan <lizefan@huawei.com>
To: Josef Bacik <jbacik@fusionio.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: kill free_space pointer from inode structure
Date: Thu, 12 Jul 2012 09:38:11 +0800 [thread overview]
Message-ID: <4FFE2A83.3050604@huawei.com> (raw)
In-Reply-To: <20120710192953.GF7529@localhost.localdomain>
On 2012/7/11 3:29, Josef Bacik wrote:
> On Mon, Jul 09, 2012 at 08:21:07PM -0600, Li Zefan wrote:
>> Inodes always allocate free space with BTRFS_BLOCK_GROUP_DATA type,
>> which means every inode has the same BTRFS_I(inode)->free_space pointer.
>>
>> This shrinks struct btrfs_inode by 4 bytes (or 8 bytes on 64 bits).
>>
>> Signed-off-by: Li Zefan <lizefan@huawei.com>
>
> Li I can't apply any of your patches because they are all in base64 format and
> I'm having a hell of a time pulling them out to apply them, can you resend with
> git send-email or something so I can apply them properly? Thanks,
>
Hmm.. I got no complaints from Tejun or Chris before, so I didn't realize all
the emails I sent were in base64. It should be the email server that encoded
my patches, so I don't think using git-send-email will make any difference.
(not to mention I failed to make git-send-email work in my office :(
Is it ok if I attach the patches in attachments? Otherwise I'll use gmail
instead when I'm at home.
next prev parent reply other threads:[~2012-07-12 1:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 2:21 [PATCH] Btrfs: kill free_space pointer from inode structure Li Zefan
2012-07-10 19:29 ` Josef Bacik
2012-07-12 1:38 ` Li Zefan [this message]
2012-07-12 13:27 ` Josef Bacik
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=4FFE2A83.3050604@huawei.com \
--to=lizefan@huawei.com \
--cc=jbacik@fusionio.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;
as well as URLs for NNTP newsgroup(s).