From: Christoph Hellwig <hch@infradead.org>
To: Vyacheslav Dubeyko <slava@dubeyko.com>
Cc: Christoph Hellwig <hch@infradead.org>,
viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] hfsplus: use xattr handlers for removexattr
Date: Thu, 30 Jan 2014 00:17:55 -0800 [thread overview]
Message-ID: <20140130081755.GA664@infradead.org> (raw)
In-Reply-To: <A6A9CDFF-6EC0-4797-B57D-7B0F630510A9@dubeyko.com>
On Thu, Jan 30, 2014 at 12:19:48PM +0300, Vyacheslav Dubeyko wrote:
> As I remember, we discussed this changes in the scope of big
> patchset. So, as far as I can judge, you simply decided to extract it
> in one patch. Am I correct?
Well, Al pulled in the earlier version of the patch, so we'll need this
one as a fixup.
> But how is this change safe without generic part of code?
> Especially, for the case of "osx." prefix. Or, maybe, I missed
> some commits in the kernel?
Yeah, the older version got merged via Al's tree.
next prev parent reply other threads:[~2014-01-30 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 7:59 [PATCH] hfsplus: use xattr handlers for removexattr Christoph Hellwig
2014-01-30 9:19 ` Vyacheslav Dubeyko
2014-01-30 8:17 ` Christoph Hellwig [this message]
2014-01-30 9:28 ` Vyacheslav Dubeyko
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=20140130081755.GA664@infradead.org \
--to=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=slava@dubeyko.com \
--cc=viro@zeniv.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox