From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Nickolaus Woodruff <nickolauswoodruff@gmail.com>
Cc: olegdrokin@intel.com, andreasdilger@intel.com,
gregkh@linuxfoundation.org, HPDD-discuss@ml01.01.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: lustre: Make cfs_sched_rehash static
Date: Tue, 7 Apr 2015 15:12:23 +0530 [thread overview]
Message-ID: <20150407094223.GB20278@sudip-PC> (raw)
In-Reply-To: <20150407020227.GA1500@Caladan>
On Mon, Apr 06, 2015 at 10:02:27PM -0400, Nickolaus Woodruff wrote:
> This patch fixes the following sparse warning:
>
> CHECK drivers/staging/lustre/lustre/libcfs/hash.c
> drivers/staging/lustre/lustre/libcfs/hash.c:119:21: warning: symbol
> 'cfs_sched_rehash' was not declared. Should it be static?
you have not build tested your patch.
WARNING: "cfs_sched_rehash" [drivers/staging/lustre/lustre/libcfs/libcfs.ko] undefined!
it has been used in lustre/lustre/libcfs/module.c
regards
sudip
>
next prev parent reply other threads:[~2015-04-07 9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 2:02 [PATCH] staging: lustre: Make cfs_sched_rehash static Nickolaus Woodruff
2015-04-07 9:42 ` Sudip Mukherjee [this message]
2015-04-07 16:01 ` [HPDD-discuss] " Drokin, Oleg
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=20150407094223.GB20278@sudip-PC \
--to=sudipm.mukherjee@gmail.com \
--cc=HPDD-discuss@ml01.01.org \
--cc=andreasdilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickolauswoodruff@gmail.com \
--cc=olegdrokin@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