From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Junien Fridrick <linux.kernel@junien.fridrick.net>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
HPDD-discuss@ml01.01.org, Peng Tao <bergwolf@gmail.com>,
Andreas Dilger <andreas.dilger@intel.com>,
Doug Oucharek <doug.s.oucharek@intel.com>,
Oleg Drokin <oleg.drokin@intel.com>,
LABBE Corentin <clabbe.montjoie@gmail.com>,
Isaac Huang <he.huang@intel.com>
Subject: Re: [PATCH] staging: lustre: fix sparse warning for static declarations
Date: Wed, 29 Oct 2014 16:36:10 +0800 [thread overview]
Message-ID: <20141029083610.GA9261@kroah.com> (raw)
In-Reply-To: <1414264176-2546-1-git-send-email-linux.kernel@junien.fridrick.net>
On Sat, Oct 25, 2014 at 07:09:34PM +0000, Junien Fridrick wrote:
> This patch fixes the following sparse warnings :
>
> drivers/staging/lustre/lnet/lnet/router_proc.c:167:5: warning: symbol 'proc_lnet_routes' was not declared. Should it be static?
> drivers/staging/lustre/lnet/lnet/router_proc.c:293:5: warning: symbol 'proc_lnet_routers' was not declared. Should it be static?
> drivers/staging/lustre/lnet/lnet/router_proc.c:428:5: warning: symbol 'proc_lnet_peers' was not declared. Should it be static?
> drivers/staging/lustre/lnet/lnet/router_proc.c:660:5: warning: symbol 'proc_lnet_nis' was not declared. Should it be static?
>
> Signed-off-by: Junien Fridrick <linux.kernel@junien.fridrick.net>
> ---
> This patch is part of task 16 of the Eudyptula challenge
> Applies to next-20141023
>
> drivers/staging/lustre/lnet/lnet/router_proc.c | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
This patch fails to apply to my tree, please refresh and try again.
thanks,
greg k-h
prev parent reply other threads:[~2014-10-29 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 19:09 [PATCH] staging: lustre: fix sparse warning for static declarations Junien Fridrick
2014-10-29 8:36 ` Greg Kroah-Hartman [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=20141029083610.GA9261@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=HPDD-discuss@ml01.01.org \
--cc=andreas.dilger@intel.com \
--cc=bergwolf@gmail.com \
--cc=clabbe.montjoie@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=doug.s.oucharek@intel.com \
--cc=he.huang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.kernel@junien.fridrick.net \
--cc=oleg.drokin@intel.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