From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"colin.king@canonical.com" <colin.king@canonical.com>,
"target-devel@vger.kernel.org" <target-devel@vger.kernel.org>,
"nab@linux-iscsi.org" <nab@linux-iscsi.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH] target/iscsi: make function target_parse_xcopy_cmd static
Date: Thu, 11 May 2017 13:55:58 +0000 [thread overview]
Message-ID: <1494510957.3018.1.camel@sandisk.com> (raw)
In-Reply-To: <20170511101616.19790-1-colin.king@canonical.com>
On Thu, 2017-05-11 at 11:16 +0100, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Making target_parse_xcopy_cmd static fixes sparse warning:
>
> "warning: symbol 'target_parse_xcopy_cmd' was not declared. Should
> it be static?"
>
> Fixes: 1bd05294519f76 ("target/iscsi: Fix a deadlock between the XCOPY code and session shutdown")
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/target/target_core_xcopy.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/target/target_core_xcopy.c b/drivers/target/target_core_xcopy.c
> index aecb36d955f0..00e0269e6be4 100644
> --- a/drivers/target/target_core_xcopy.c
> +++ b/drivers/target/target_core_xcopy.c
> @@ -886,7 +886,7 @@ static void target_xcopy_do_work(struct work_struct *work)
> * Returns TCM_NO_SENSE upon success or a sense code != TCM_NO_SENSE if parsing
> * fails.
> */
> -sense_reason_t target_parse_xcopy_cmd(struct xcopy_op *xop)
> +static sense_reason_t target_parse_xcopy_cmd(struct xcopy_op *xop)
> {
> struct se_cmd *se_cmd = xop->xop_se_cmd;
> unsigned char *p = NULL, *seg_desc;
Hello Colin,
Thanks for the patch. I will merge it in patch "target/iscsi: Fix a deadlock between the
XCOPY code and session shutdown".
Bart.
next prev parent reply other threads:[~2017-05-11 13:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 10:16 Colin King
2017-05-11 13:55 ` Bart Van Assche [this message]
2017-05-11 13:58 ` Colin Ian King
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=1494510957.3018.1.camel@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=target-devel@vger.kernel.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
all inboxes | Powered by JetHome®