public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
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>,
	"target-devel@vger.kernel.org" <target-devel@vger.kernel.org>
Subject: Re: target: fixup error message in target_tg_pt_gp_tg_pt_gp_id_store()
Date: Thu, 27 Apr 2017 16:17:09 +0000	[thread overview]
Message-ID: <1493309828.2625.8.camel@sandisk.com> (raw)
In-Reply-To: <1493302638-113622-1-git-send-email-hare@suse.de>

On Thu, 2017-04-27 at 16:17 +0200, Hannes Reinecke wrote:
> When setting up an ALUA target port group with an invalid ID the
> error message
> 
> kstrtoul() returned -22 for tg_pt_gp_id
> 
> is displayed, which is not really helpful.
> Convert it to something sane.
> 
> Reviewed-by: Hannes Reinecke <hare@suse.com>

Did you perhaps mean "Signed-off-by"?

>  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 1f229cc..27f7411 100644
> --- a/drivers/target/target_core_configfs.c
> +++ b/drivers/target/target_core_configfs.c
> @@ -2691,8 +2691,8 @@ static ssize_t target_tg_pt_gp_tg_pt_gp_id_store(struct config_item *item,
>  
>  	ret = kstrtoul(page, 0, &tg_pt_gp_id);
>  	if (ret < 0) {
> -		pr_err("kstrtoul() returned %d for"
> -			" tg_pt_gp_id\n", ret);
> +		pr_err("ALUA tg_pt_gp_id: invalid value '%s' for"
> +			" tg_pt_gp_id\n", page);
>  		return ret;
>  	}
>  	if (tg_pt_gp_id > 0x0000ffff) {

Although this patch looks fine to me, this would have been a good opportunity
to join the two parts of the error message such that these appear on the same
source code line.

Bart.

      reply	other threads:[~2017-04-27 16:17 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_tg_pt_gp_id_store() Hannes Reinecke
2017-04-27 16:17 ` 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=1493309828.2625.8.camel@sandisk.com \
    --to=bart.vanassche@sandisk.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