From: Oleg Drokin <oleg.drokin@intel.com>
To: "<sandeepjain.linux@gmail.com>" <sandeepjain.linux@gmail.com>
Cc: <andreas.dilger@intel.com>, <jsimmons@infradead.org>,
<gregkh@linuxfoundation.org>, <lustre-devel@lists.lustre.org>,
<devel@driverdev.osuosl.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: lustre: mgc: make llog_process_lock static
Date: Mon, 5 Dec 2016 17:48:11 -0500 [thread overview]
Message-ID: <57EFF4DF-FEA7-40D5-AD29-4DF3E16D047B@intel.com> (raw)
In-Reply-To: <1480904481-20149-1-git-send-email-sandeepjain.linux@gmail.com>
On Dec 4, 2016, at 9:21 PM, <sandeepjain.linux@gmail.com> <sandeepjain.linux@gmail.com> wrote:
> From: Sandeep Jain <sandeepjain.linux@gmail.com>
>
> Fix following sparse warning.
> mgc_request.c:376:1:
> warning: symbol 'llog_process_lock' was not declared. Should it be static?
>
> Signed-off-by: Sandeep Jain <sandeepjain.linux@gmail.com>
Acked-by: Oleg Drokin <oleg.drokin@intel.com>
> ---
> drivers/staging/lustre/lustre/mgc/mgc_request.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/lustre/lustre/mgc/mgc_request.c b/drivers/staging/lustre/lustre/mgc/mgc_request.c
> index 23600fb..e98a2ce 100644
> --- a/drivers/staging/lustre/lustre/mgc/mgc_request.c
> +++ b/drivers/staging/lustre/lustre/mgc/mgc_request.c
> @@ -373,7 +373,7 @@ static int config_log_add(struct obd_device *obd, char *logname,
> return rc;
> }
>
> -DEFINE_MUTEX(llog_process_lock);
> +static DEFINE_MUTEX(llog_process_lock);
>
> /** Stop watching for updates on this log.
> */
> --
> 2.7.4
prev parent reply other threads:[~2016-12-05 22:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 2:21 sandeepjain.linux
2016-12-05 22:48 ` Oleg Drokin [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=57EFF4DF-FEA7-40D5-AD29-4DF3E16D047B@intel.com \
--to=oleg.drokin@intel.com \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=sandeepjain.linux@gmail.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
Powered by JetHome