public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@kernel.org>
To: Minjie Du <duminjie@vivo.com>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	"open list:I2C SUBSYSTEM HOST DRIVERS"
	<linux-i2c@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	opensource.kernel@vivo.com, stable@vger.kernel.org,
	Markus Elfring <Markus.Elfring@web.de>
Subject: Re: [PATCH v3] i2c: busses: fix parameter check in i2c_gpio_fault_injector_init()
Date: Thu, 13 Jul 2023 11:50:18 +0200	[thread overview]
Message-ID: <20230713095018.3v6qhc3y7bsic6ha@intel.intel> (raw)
In-Reply-To: <20230713020517.614-1-duminjie@vivo.com>

Hi Minje,

as Markus suggested, the title

“i2c: gpio: Fix an error check in i2c_gpio_fault_injector_init()”

looks more appropriate and...

On Thu, Jul 13, 2023 at 10:05:17AM +0800, Minjie Du wrote:
> Make IS_ERR() judge the debugfs_create_dir() function return.

... I think you should fix a bit the log here (also Mark has
suggested it). How about something like:

debugfs_create_dir() function returns an error value embedded in
the pointer (PTR_ERR). We need to evaluate the return value using
IS_ERR, rather than checking for NULL.

> Fixes: 14911c6f48ec ("i2c: gpio: add fault injector")
> Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>
> Cc: <stable@vger.kernel.org> # v4.16+
> 

don't leave space between tags.

> Signed-off-by: Minjie Du <duminjie@vivo.com>
> Reviewed-by: Andi Shyti <andi.shyti@kernel.org>

At the end it can be something like:

   i2c: gpio: Fix an error check in i2c_gpio_fault_injector_init()
   
   debugfs_create_dir() function returns an error value embedded in 
   the pointer (PTR_ERR). Evaluate the return value using IS_ERR
   rather than checking for NULL.
   
   Fixes: 14911c6f48ec ("i2c: gpio: add fault injector")          
   Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>
   Cc: <stable@vger.kernel.org> # v4.16+
   Signed-off-by: Minjie Du <duminjie@vivo.com>
   Reviewed-by: Andi Shyti <andi.shyti@kernel.org>

I'm not sure whether Wolfram can fix it or, if you don't feel
lazy, you can send a v4.

> ---
> v1-v2:
> Fix judge typo.

Please update also the changelog, v2-v3 and v3-v4.

Thanks, Markus, for the suggestions.

Andi

> ---
>  drivers/i2c/busses/i2c-gpio.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/i2c/busses/i2c-gpio.c b/drivers/i2c/busses/i2c-gpio.c
> index e5a5b9e8b..545927b96 100644
> --- a/drivers/i2c/busses/i2c-gpio.c
> +++ b/drivers/i2c/busses/i2c-gpio.c
> @@ -265,7 +265,7 @@ static void i2c_gpio_fault_injector_init(struct platform_device *pdev)
>  	 */
>  	if (!i2c_gpio_debug_dir) {
>  		i2c_gpio_debug_dir = debugfs_create_dir("i2c-fault-injector", NULL);
> -		if (!i2c_gpio_debug_dir)
> +		if (IS_ERR(i2c_gpio_debug_dir))
>  			return;
>  	}
>  
> -- 
> 2.39.0
> 

  reply	other threads:[~2023-07-13  9:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-13  2:05 [PATCH v3] i2c: busses: fix parameter check in i2c_gpio_fault_injector_init() Minjie Du
2023-07-13  9:50 ` Andi Shyti [this message]
     [not found] ` <d6d04803-0dc1-9565-23b4-740425066a01@web.de>
2023-07-13  9:53   ` Andi Shyti

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=20230713095018.3v6qhc3y7bsic6ha@intel.intel \
    --to=andi.shyti@kernel.org \
    --cc=Markus.Elfring@web.de \
    --cc=duminjie@vivo.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=opensource.kernel@vivo.com \
    --cc=stable@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.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