From: Greg KH <gregkh@linuxfoundation.org>
To: Eli Billauer <eli.billauer@gmail.com>
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org, corbet@lwn.net
Subject: Re: [PATCH v3 2/7] char: xillybus: Remove duplicate error path code
Date: Fri, 31 Jul 2026 14:25:52 +0200 [thread overview]
Message-ID: <2026073157-wasp-amid-2729@gregkh> (raw)
In-Reply-To: <20260724094302.50761-3-eli.billauer@gmail.com>
On Fri, Jul 24, 2026 at 11:42:57AM +0200, Eli Billauer wrote:
> No need for dedicated code for the error path. The removed dedicated
> error path code differs only in when the mutex is released, and that
> makes no difference in this context.
>
> Assisted-by: Deepseek:v4-pro Kimi:K2.6 ChatGPT:GPT-5.5 Claude:Sonnet-4.6
> Signed-off-by: Eli Billauer <eli.billauer@gmail.com>
> ---
>
> Notes:
> Changes v2->v3:
> -- Add Assisted-by tag to description
>
> No change on v1->v2.
>
> drivers/char/xillybus/xillyusb.c | 6 +-----
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
> diff --git a/drivers/char/xillybus/xillyusb.c b/drivers/char/xillybus/xillyusb.c
> index a28e6416cb01..ab5f9159aa17 100644
> --- a/drivers/char/xillybus/xillyusb.c
> +++ b/drivers/char/xillybus/xillyusb.c
> @@ -1419,16 +1419,12 @@ static int xillyusb_open(struct inode *inode, struct file *filp)
> if (filp->f_mode & FMODE_WRITE)
> chan->open_for_write = 0;
>
> +unmutex_fail:
> mutex_unlock(&chan->lock);
>
> kref_put(&xdev->kref, cleanup_dev);
>
> return rc;
> -
> -unmutex_fail:
> - kref_put(&xdev->kref, cleanup_dev);
> - mutex_unlock(&chan->lock);
> - return rc;
> }
>
> static ssize_t xillyusb_read(struct file *filp, char __user *userbuf,
> --
> 2.34.1
>
Again, some sashiko comments seem like this might not be the correct
changelog text:
https://sashiko.dev/#/patchset/20260724094302.50761-1-eli.billauer@gmail.com
Can you verify that the other comments in that review for this series
isn't also valid (or not?)
thanks,
greg k-h
next prev parent reply other threads:[~2026-07-31 12:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 9:42 [PATCH v3 0/7] char: xillybus: Harden driver and improve code quality Eli Billauer
2026-07-24 9:42 ` [PATCH v3 1/7] char: xillybus: Improve control of execution flow with mutexes Eli Billauer
2026-07-31 12:24 ` Greg KH
2026-07-24 9:42 ` [PATCH v3 2/7] char: xillybus: Remove duplicate error path code Eli Billauer
2026-07-31 12:25 ` Greg KH [this message]
2026-07-24 9:42 ` [PATCH v3 3/7] char: xillybus: Avoid possible bandwidth inefficiency Eli Billauer
2026-07-24 9:42 ` [PATCH v3 4/7] char: xillybus: Use unsigned arithmetic for jiffies differences Eli Billauer
2026-07-24 9:43 ` [PATCH v3 5/7] char: xillybus: Integer arithmetic improvements Eli Billauer
2026-07-24 9:43 ` [PATCH v3 6/7] char: xillybus: Add defensive sanity checks Eli Billauer
2026-07-24 9:43 ` [PATCH v3 7/7] char: xillybus: Ignore and report unsolicited interrupts Eli Billauer
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=2026073157-wasp-amid-2729@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=eli.billauer@gmail.com \
--cc=linux-kernel@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
Powered by JetHome