public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Dominik Karol Piątkowski" <dominik.karol.piatkowski@protonmail.com>
Cc: Dave Penkler <dpenkler@gmail.com>,
	Michael Rubin <matchstick@neverthere.org>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/9] gpib: agilent_82350b: Unify *allocate_private
Date: Fri, 16 Jan 2026 08:36:36 +0100	[thread overview]
Message-ID: <2026011649-glitter-unawake-3f50@gregkh> (raw)
In-Reply-To: <20260113190759.54355-2-dominik.karol.piatkowski@protonmail.com>

On Tue, Jan 13, 2026 at 07:08:43PM +0000, Dominik Karol Piątkowski wrote:
> Return values for *allocate_private functions as well as calling code in
> gpib driver are all over the place. Unify them by returning -errno if
> something fails, zero otherwise. Use the returned value as early return
> value in case of error.
> 
> Signed-off-by: Dominik Karol Piątkowski <dominik.karol.piatkowski@protonmail.com>
> ---
>  drivers/gpib/agilent_82350b/agilent_82350b.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpib/agilent_82350b/agilent_82350b.c b/drivers/gpib/agilent_82350b/agilent_82350b.c
> index 01a5bb43cd2d..f5f102863e47 100644
> --- a/drivers/gpib/agilent_82350b/agilent_82350b.c
> +++ b/drivers/gpib/agilent_82350b/agilent_82350b.c
> @@ -599,8 +599,9 @@ static int agilent_82350b_generic_attach(struct gpib_board *board,
>  
>  	board->status = 0;
>  
> -	if (agilent_82350b_allocate_private(board))
> -		return -ENOMEM;
> +	retval = agilent_82350b_allocate_private(board);
> +	if (retval < 0)
> +		return retval;

This should be:
	if (retval)
		return retval;

right?

And the function only returns either 0 or -ENOMEM, so your changelog
text is not correct.

thanks,

greg k-h

  reply	other threads:[~2026-01-16  7:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-13 19:08 [PATCH 0/9] gpib: Unify *allocate_private Dominik Karol Piątkowski
2026-01-13 19:08 ` [PATCH 1/9] gpib: agilent_82350b: " Dominik Karol Piątkowski
2026-01-16  7:36   ` Greg Kroah-Hartman [this message]
2026-01-16 14:45     ` Dominik Karol Piątkowski
2026-01-13 19:08 ` [PATCH 2/9] gpib: cb7210: " Dominik Karol Piątkowski
2026-01-13 19:08 ` [PATCH 3/9] gpib: cec: " Dominik Karol Piątkowski
2026-01-15 16:29   ` Dave Penkler
2026-01-15 18:11     ` Dominik Karol Piątkowski
2026-01-16  7:50     ` Greg Kroah-Hartman
2026-01-13 19:09 ` [PATCH 4/9] gpib: gpio: " Dominik Karol Piątkowski
2026-01-13 19:09 ` [PATCH 5/9] gpib: hp_82335: " Dominik Karol Piątkowski
2026-01-13 19:09 ` [PATCH 6/9] gpib: hp_82341: " Dominik Karol Piątkowski
2026-01-13 19:09 ` [PATCH 7/9] gpib: ines: " Dominik Karol Piątkowski
2026-01-13 19:09 ` [PATCH 8/9] gpib: pc2: " Dominik Karol Piątkowski
2026-01-13 19:09 ` [PATCH 9/9] gpib: tnt4882: " Dominik Karol Piątkowski
2026-01-19  7:34 ` [PATCH 0/9] gpib: " Dan Carpenter
2026-01-20 16:12   ` Dominik Karol Piątkowski

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=2026011649-glitter-unawake-3f50@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dan.carpenter@linaro.org \
    --cc=dominik.karol.piatkowski@protonmail.com \
    --cc=dpenkler@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matchstick@neverthere.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