From: Boaz Harrosh <bharrosh@panasas.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Al Viro <viro@ftp.linux.org.uk>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 47/58] convert exofs to ->evict_inode()
Date: Wed, 09 Jun 2010 14:09:07 +0300 [thread overview]
Message-ID: <4C0F7653.9080207@panasas.com> (raw)
In-Reply-To: <20100609100213.GC15403@lst.de>
On 06/09/2010 01:02 PM, Christoph Hellwig wrote:
> On Wed, Jun 09, 2010 at 12:05:36PM +0300, Boaz Harrosh wrote:
>> On 06/09/2010 01:22 AM, Al Viro wrote:
>>>
>>> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
>>
>> Al hi.
>>
>> This patch is nice off course, but it clashes with a patch
>> I was intending to push to linux-next today. (For 2.6.36 kernel)
>>
>> The patch is the one to convert to the new truncate sequence:
>> http://marc.info/?l=linux-fsdevel&m=127539189718732&w=2
>>
>> In fact I was meaning to ask you if you could take this patch
>> through your tree, so Christoph could base his cleanup on this
>> as well.
>
> The new truncate sequence bits already are in Al's tree. And as
> I said a few times before life would really be a lot simpler if
> you just base things ontop of that. It makes the API for the
> file system a lot better.
>
Will do. Patch based on vfs/for-next posted as reply.
(Please review?)
Al's patch thing still holds, Al?
Boaz
next prev parent reply other threads:[~2010-06-09 11:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 22:22 [PATCH 47/58] convert exofs to ->evict_inode() Al Viro
2010-06-09 9:05 ` Boaz Harrosh
2010-06-09 10:02 ` Christoph Hellwig
2010-06-09 11:09 ` Boaz Harrosh [this message]
2010-06-09 11:10 ` [PATCH ver4] exofs: New truncate sequence Boaz Harrosh
2010-06-09 11:13 ` Boaz Harrosh
2010-06-09 12:45 ` Al Viro
2010-06-09 13:43 ` Boaz Harrosh
2010-06-09 21:46 ` Al Viro
2010-06-10 12:40 ` Boaz Harrosh
2010-06-09 13:55 ` Christoph Hellwig
2010-06-09 15:26 ` Boaz Harrosh
2010-06-09 15:23 ` [PATCH ver5] " Boaz Harrosh
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=4C0F7653.9080207@panasas.com \
--to=bharrosh@panasas.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.