On Tue, Nov 26, 2013 at 07:13:18PM -0800, Darrick J. Wong wrote: > On Wed, Nov 27, 2013 at 10:52:32AM +0800, Zheng Liu wrote: > > On Tue, Nov 26, 2013 at 11:55:47AM -0800, Darrick J. Wong wrote: > > > On Tue, Nov 26, 2013 at 03:21:16PM +0800, Zheng Liu wrote: > > > > On Thu, Oct 17, 2013 at 09:51:34PM -0700, Darrick J. Wong wrote: > > > > > Add functions to allow clients to get, set, and remove extended > > > > > attributes from any file. It also supports modifying EAs living in > > > > > i_file_acl. > > > > > > > > > > v2: Put the header declarations in the correct part of ext2fs.h, > > > > > provide a function to release an EA block from an inode, and check > > > > > i_extra_isize to make sure we actually have space for in-inode EAs. > > > > > > > > Is this the latest version? I am working on inline data patch set for > > > > e2fsprogs, and I want to use these API to manipulate the EA. So that > > > > would be great if you could point out which one is the latest version. > > > > Thanks in advance. Otherwise some nits below. > > > > > > Oh! I was just about to start working on pulling your patches into my monster > > > patchset. :) > > > > Wow! Sorry for my late. If you just begin to work on inline data > > patchset. Would you mind sending your latest monster patchset without > > my inline data patchset first? That gives me a chance to take a closer > > look at them. In general, I will send my patch set asap. > > Don't worry about the timing. I've been busy with a lot of other things. > Every time I think I'm done and can start on inline_data, I find another weird > test case that breaks things, so I have to go back and figure out what went > wrong. > > The patchbomb lives here: https://djwong.org/docs/e2fsprogs-patches/ > > Patch 22 is the end of my last (Oct. 2013) patchbomb. I think the relevant > ones you want are #20 and #24-32. You can skip #26-27 if you don't care about > fuse2fs. Got it. Thanks for your help. :) - Zheng -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
