From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Enze Li <lienze@kylinos.cn>
Cc: jejb@linux.ibm.com, martin.petersen@oracle.com,
linux-scsi@vger.kernel.org, enze.li@gmx.com
Subject: Re: [PATCH] scsi: sr: simplify the sr_open function
Date: Sun, 02 Apr 2023 21:37:00 -0400 [thread overview]
Message-ID: <yq14jpxyceg.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20230327030237.3407253-1-lienze@kylinos.cn> (Enze Li's message of "Mon, 27 Mar 2023 11:02:37 +0800")
Enze,
> Simplify the sr_open function by removing the goto label as it does only
> return one error code.
Applied to 6.4/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2023-04-03 1:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 3:02 [PATCH] scsi: sr: simplify the sr_open function Enze Li
2023-03-29 20:50 ` Bart Van Assche
2023-03-30 14:46 ` Benjamin Block
2023-04-03 1:37 ` Martin K. Petersen [this message]
2023-04-12 2:04 ` Martin K. Petersen
-- strict thread matches above, loose matches on Subject: below --
2022-09-16 9:04 Enze Li
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=yq14jpxyceg.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=enze.li@gmx.com \
--cc=jejb@linux.ibm.com \
--cc=lienze@kylinos.cn \
--cc=linux-scsi@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