Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Honggang Li <honli@redhat.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [rdma-core patch] srp_daemon: improve the debug message for is_enabled_by_rules_file
Date: Thu, 11 Jul 2019 11:29:32 -0700	[thread overview]
Message-ID: <5bee2fbe-c255-fc1d-b7c3-4757e5d8569c@acm.org> (raw)
In-Reply-To: <20190711024001.14648-1-honli@redhat.com>

On 7/10/19 7:40 PM, Honggang Li wrote:
> Signed-off-by: Honggang Li <honli@redhat.com>
> ---
>  srp_daemon/srp_daemon.c | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/srp_daemon/srp_daemon.c b/srp_daemon/srp_daemon.c
> index a004f6a4..f27dd569 100644
> --- a/srp_daemon/srp_daemon.c
> +++ b/srp_daemon/srp_daemon.c
> @@ -349,10 +349,11 @@ static int is_enabled_by_rules_file(struct target_details *target)
>  	int rule;
>  	struct config_t *conf = config;
>  
> -	if (NULL == conf->rules)
> +	if (NULL == conf->rules) {
> +		pr_debug("SRP target with id_ext %s allowed by rules file\n", target->id_ext);
>  		return 1;
> +	}

How about changing that message into e.g. "Allowing SRP target with
id_ext %s because not using a rules file"?

> +		pr_debug("SRP target with id_ext %s %s by rules file\n",
> +				target->id_ext,
> +				conf->rules[rule].allow == 1 ? "allowed" : "disallowed");
>  		return conf->rules[rule].allow;

Is the "== 1" part necessary?

Otherwise this patch looks good to me.

Thanks,

Bart.


      reply	other threads:[~2019-07-11 18:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-11  2:40 [rdma-core patch] srp_daemon: improve the debug message for is_enabled_by_rules_file Honggang Li
2019-07-11 18:29 ` 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=5bee2fbe-c255-fc1d-b7c3-4757e5d8569c@acm.org \
    --to=bvanassche@acm.org \
    --cc=honli@redhat.com \
    --cc=linux-rdma@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