From: Bart Van Assche <bvanassche@acm.org>
To: "Bean Huo (beanhuo)" <beanhuo@micron.com>,
Avri Altman <Avri.Altman@wdc.com>,
"huobean@gmail.com" <huobean@gmail.com>,
"alim.akhtar@samsung.com" <alim.akhtar@samsung.com>,
"asutoshd@codeaurora.org" <asutoshd@codeaurora.org>,
"jejb@linux.ibm.com" <jejb@linux.ibm.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"stanley.chu@mediatek.com" <stanley.chu@mediatek.com>,
"tomas.winkler@intel.com" <tomas.winkler@intel.com>,
"cang@codeaurora.org" <cang@codeaurora.org>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [EXT] RE: [PATCH 0/1] Revert "scsi: ufs: Let the SCSI core allocate per-command UFS data"
Date: Wed, 11 Mar 2020 07:02:54 -0700 [thread overview]
Message-ID: <cfa5b0c8-1ca6-5d1c-591b-67e783d979fd@acm.org> (raw)
In-Reply-To: <BN7PR08MB5684DBAD57C95A40CB62B24ADBFC0@BN7PR08MB5684.namprd08.prod.outlook.com>
On 3/11/20 5:53 AM, Bean Huo (beanhuo) wrote:
> Hi, Avri
> Do you want to revert all or two (scsi: ufs: Let the SCSI core allocate per-command UFS data, scsi: core: Introduce {init,exit}_cmd_priv() )?
> Because the patches "scsi: ufs: Simplify two tests" and "scsi: ufs: Introduce ufshcd_init_lrb()" are ok to me.
> No problem keeping them. Just this one "scsi: core: Introduce {init,exit}_cmd_priv()" is not necessary, since no drivers it now.
I agree with Bean. The other patches from the same series are small and
easy to review. The SCSI core patch has been tested with other SCSI LLDs.
Bart.
prev parent reply other threads:[~2020-03-11 14:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 11:29 huobean
2020-03-11 11:29 ` [PATCH 1/1] " huobean
2020-03-12 3:08 ` Martin K. Petersen
2020-03-11 12:25 ` [PATCH 0/1] " Avri Altman
2020-03-11 12:53 ` [EXT] " Bean Huo (beanhuo)
2020-03-11 14:02 ` Bart Van Assche [this message]
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=cfa5b0c8-1ca6-5d1c-591b-67e783d979fd@acm.org \
--to=bvanassche@acm.org \
--cc=Avri.Altman@wdc.com \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=beanhuo@micron.com \
--cc=cang@codeaurora.org \
--cc=huobean@gmail.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=stanley.chu@mediatek.com \
--cc=tomas.winkler@intel.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®