From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "hare@suse.de" <hare@suse.de>, "nab@daterainc.com" <nab@daterainc.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"hare@suse.com" <hare@suse.com>,
"target-devel@vger.kernel.org" <target-devel@vger.kernel.org>
Subject: Re: target: fixup error message in target_tg_pt_gp_alua_access_type_store()
Date: Thu, 27 Apr 2017 16:14:50 +0000 [thread overview]
Message-ID: <1493309687.2625.5.camel@sandisk.com> (raw)
In-Reply-To: <1493302624-113570-1-git-send-email-hare@suse.de>
On Thu, 2017-04-27 at 16:17 +0200, Hannes Reinecke wrote:
> When setting up a target the error message:
>
> Unable to do set ##_name ALUA state on non valid tg_pt_gp ID: 0
>
> is displayed.
> Apparently concatenation doesn't work in a string; one should be using
> implicit string concatenation here.
>
> Signed-off-by: Hannes Reinecke <hare@suse.com>
> ---
> drivers/target/target_core_configfs.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/target/target_core_configfs.c b/drivers/target/target_core_configfs.c
> index dc654fe..1f229cc 100644
> --- a/drivers/target/target_core_configfs.c
> +++ b/drivers/target/target_core_configfs.c
> @@ -2559,9 +2559,9 @@ static ssize_t target_tg_pt_gp_alua_support_##_name##_store( \
> int ret; \
> \
> if (!t->tg_pt_gp_valid_id) { \
> - pr_err("Unable to do set ##_name ALUA state on non" \
> + pr_err("Unable to do set " #_name " ALUA state on non" \
> " valid tg_pt_gp ID: %hu\n", \
> - t->tg_pt_gp_valid_id); \
> + t->tg_pt_gp_valid_id); \
> return -EINVAL; \
> } \
Hello Hannes,
The second change breaks the alignment of the backspaces which is unfortunate.
Otherwise this patch looks fine to me.
Bart. \
prev parent reply other threads:[~2017-04-27 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 14:17 target: fixup error message in target_tg_pt_gp_alua_access_type_store() Hannes Reinecke
2017-04-27 16:14 ` Bart Van Assche [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=1493309687.2625.5.camel@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=hare@suse.com \
--cc=hare@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@daterainc.com \
--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