From: Tejun Heo <tj@kernel.org>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: Dr Fields James Bruce <bfields@fieldses.org>,
linuxnfs <linux-nfs@vger.kernel.org>,
Li Zefan <lizefan@huawei.com>,
containers@lists.linux-foundation.org, cgroups@vger.kernel.org
Subject: Re: [PATCH] nfs: include xattr.h from fs/nfs/nfs3proc.c
Date: Mon, 3 Feb 2014 15:43:19 -0500 [thread overview]
Message-ID: <20140203204319.GI30250@htj.dyndns.org> (raw)
In-Reply-To: <F2DD11A7-8D32-4E1E-BB4D-7384F0932B2D@primarydata.com>
On Mon, Feb 03, 2014 at 02:48:13PM -0500, Trond Myklebust wrote:
>
> On Feb 3, 2014, at 14:31, Tejun Heo <tj@kernel.org> wrote:
>
> > fs/nfs/nfs3proc.c is making use of xattr but was getting linux/xattr.h
> > indirectly through linux/cgroup.h, which will soon drop the inclusion
> > of xattr.h. Explicitly include linux/xattr.h from nfs3proc.c so that
> > compilation doesn't fail when linux/cgroup.h drops linux/xattr.h.
> >
> > As the following cgroup changes will depend on these changes, it
> > probably would be easier to route this through cgroup branch. Would
> > that be okay?
> >
> > Signed-off-by: Tejun Heo <tj@kernel.org>
> > Cc: "J. Bruce Fields" <bfields@fieldses.org>
>
> EWRONGMAINTAINER… :-)
>
> Acked-by: Trond Myklebust <trond.myklebust@primarydata.com>
Oopsy, thanks! :)
--
tejun
next prev parent reply other threads:[~2014-02-03 20:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 19:31 [PATCH] nfs: include xattr.h from fs/nfs/nfs3proc.c Tejun Heo
2014-02-03 19:48 ` Trond Myklebust
2014-02-03 20:43 ` Tejun Heo [this message]
2014-02-03 20:45 ` Tejun Heo
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=20140203204319.GI30250@htj.dyndns.org \
--to=tj@kernel.org \
--cc=bfields@fieldses.org \
--cc=cgroups@vger.kernel.org \
--cc=containers@lists.linux-foundation.org \
--cc=linux-nfs@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=trond.myklebust@primarydata.com \
/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