From: Bean Huo <huobean@gmail.com>
To: Avri Altman <avri.altman@wdc.com>,
"James E . J . Bottomley" <jejb@linux.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: Bart Van Assche <bvanassche@acm.org>,
Bean Huo <beanhuo@micron.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/4] scsi: ufs: Re-use exec_dev_cmd
Date: Tue, 12 Mar 2024 16:33:17 +0100 [thread overview]
Message-ID: <4aa7761173875ccfac57b18c9f002c4078358631.camel@gmail.com> (raw)
In-Reply-To: <20240309081104.5006-3-avri.altman@wdc.com>
On Sat, 2024-03-09 at 10:11 +0200, Avri Altman wrote:
> Move out the actual command issue from exec_dev_cmd so it can be used
> elsewhere. While at it, remove a redundant "lrbp->cmd = NULL"
> assignment.
>
> Also, the device management commands that are originated from the
> ufs-bsg code path, are being traced now, which wasn't the case
> before.
>
> Signed-off-by: Avri Altman <avri.altman@wdc.com>
Reviewed-by: Bean Huo <beanhuo@micron.com>
next prev parent reply other threads:[~2024-03-12 15:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 8:10 [PATCH v3 0/4] Re-use device management code fragments Avri Altman
2024-03-09 8:10 ` [PATCH v3 1/4] scsi: ufs: Re-use device management locking code Avri Altman
2024-03-09 8:11 ` [PATCH v3 2/4] scsi: ufs: Re-use exec_dev_cmd Avri Altman
2024-03-11 18:35 ` Bart Van Assche
2024-03-12 15:33 ` Bean Huo [this message]
2024-03-09 8:11 ` [PATCH v3 3/4] scsi: ufs: Re-use compose_dev_cmd Avri Altman
2024-03-09 8:11 ` [PATCH v3 4/4] scsi: ufs: Re-use compose_devman_upiu Avri Altman
2024-03-11 18:36 ` Bart Van Assche
2024-03-12 15:34 ` Bean Huo
2024-03-23 10:06 ` [PATCH v3 0/4] Re-use device management code fragments Avri Altman
2024-03-25 20:52 ` Martin K. Petersen
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=4aa7761173875ccfac57b18c9f002c4078358631.camel@gmail.com \
--to=huobean@gmail.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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
all inboxes | Powered by JetHome®