The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Eli Billauer <eli.billauer@gmail.com>
To: gregkh@linuxfoundation.org
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org,
	Eli Billauer <eli.billauer@gmail.com>
Subject: [PATCH v2 2/7] char: xillybus: Remove duplicate error path code
Date: Wed, 22 Jul 2026 12:23:02 +0200	[thread overview]
Message-ID: <20260722102307.49090-3-eli.billauer@gmail.com> (raw)
In-Reply-To: <20260722102307.49090-1-eli.billauer@gmail.com>

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.

Signed-off-by: Eli Billauer <eli.billauer@gmail.com>
---

Notes:
    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


  parent reply	other threads:[~2026-07-22 10:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22 10:23 [PATCH v2 0/7] char: xillybus: Harden driver and improve code quality Eli Billauer
2026-07-22 10:23 ` [PATCH v2 1/7] char: xillybus: Improve control of execution flow with mutexes Eli Billauer
2026-07-22 10:23 ` Eli Billauer [this message]
2026-07-22 10:23 ` [PATCH v2 3/7] char: xillybus: Avoid possible bandwidth inefficiency Eli Billauer
2026-07-22 10:23 ` [PATCH v2 4/7] char: xillybus: Use unsigned arithmetic for jiffies differences Eli Billauer
2026-07-22 10:23 ` [PATCH v2 5/7] char: xillybus: Integer arithmetic improvements Eli Billauer
2026-07-22 10:23 ` [PATCH v2 6/7] char: xillybus: Add defensive sanity checks Eli Billauer
2026-07-22 10:23 ` [PATCH v2 7/7] char: xillybus: Ignore and report unsolicited interrupts Eli Billauer
2026-07-22 14:49 ` [PATCH v2 0/7] char: xillybus: Harden driver and improve code quality Jonathan Corbet

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=20260722102307.49090-3-eli.billauer@gmail.com \
    --to=eli.billauer@gmail.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --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