From: Richard Weinberger <richard@nod.at>
To: Ben Dooks <ben.dooks@codethink.co.uk>,
linux-kernel@lists.codethink.co.uk
Cc: Artem Bityutskiy <dedekind1@gmail.com>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH] ubifs-next: make xattr structures static
Date: Tue, 21 Jun 2016 21:23:01 +0200 [thread overview]
Message-ID: <57699415.7060603@nod.at> (raw)
In-Reply-To: <1466527843-1163-1-git-send-email-ben.dooks@codethink.co.uk>
Am 21.06.2016 um 18:50 schrieb Ben Dooks:
> Fix sparse warnings from the use of "struct xattr_handler"
> structures that are not exported by making them static. Fixes
> the following sparse warnings:
>
> /fs/ubifs/xattr.c:595:28: warning: symbol 'ubifs_user_xattr_handler' was not declared. Should it be static?
> /fs/ubifs/xattr.c:601:28: warning: symbol 'ubifs_trusted_xattr_handler' was not declared. Should it be static?
> /fs/ubifs/xattr.c:607:28: warning: symbol 'ubifs_security_xattr_handler' was not declared. Should it be static?
>
> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
Makes sense!
Thanks,
//richard
prev parent reply other threads:[~2016-06-21 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 16:50 [PATCH] ubifs-next: make xattr structures static Ben Dooks
2016-06-21 19:23 ` Richard Weinberger [this message]
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=57699415.7060603@nod.at \
--to=richard@nod.at \
--cc=adrian.hunter@intel.com \
--cc=ben.dooks@codethink.co.uk \
--cc=dedekind1@gmail.com \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=linux-mtd@lists.infradead.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).