From: Bart Van Assche <bvanassche@acm.org>
To: Alim Akhtar <alim.akhtar@gmail.com>, Avri Altman <Avri.Altman@wdc.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
Kiwoong Kim <kwmad.kim@samsung.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>,
Stanley Chu <stanley.chu@mediatek.com>,
Tomas Winkler <tomas.winkler@intel.com>,
Alim Akhtar <alim.akhtar@samsung.com>
Subject: Re: [PATCH 3/3] ufs: Remove .setup_xfer_req()
Date: Tue, 5 Nov 2019 20:45:01 -0800 [thread overview]
Message-ID: <5dd9deb7-77c7-332c-6001-c6d232fa7f0d@acm.org> (raw)
In-Reply-To: <CAGOxZ53xoaFrs09KfPFHfR69-n9SnRrZ0uESE65e+Wgwe3Pr7A@mail.gmail.com>
On 2019-11-05 20:09, Alim Akhtar wrote:
> I checked the brief history of this adding "setup_xfer_req" to
> support Samsung UFSHCI (this was the ground work done)
> We need this to support vendor specific NEXUS_TYPE settings.
> The Samsung UFSHCI driver will be up for review in near future
> For usecase of the function pointer please see an older version of the
> patch https://patchwork.kernel.org/patch/7306321/
Thanks Alim for having looked up this information. Let's drop this patch.
Bart.
next prev parent reply other threads:[~2019-11-06 4:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 23:07 [PATCH 0/3] Three small UFS patches Bart Van Assche
2019-10-29 23:07 ` [PATCH 1/3] ufs: Fix kernel-doc warnings Bart Van Assche
2019-10-30 11:20 ` Avri Altman
2019-11-01 2:15 ` Martin K. Petersen
2019-10-29 23:07 ` [PATCH 2/3] ufs: Use enum dev_cmd_type where appropriate Bart Van Assche
2019-10-30 11:25 ` Avri Altman
2019-11-01 2:16 ` Martin K. Petersen
2019-10-29 23:07 ` [PATCH 3/3] ufs: Remove .setup_xfer_req() Bart Van Assche
2019-10-30 11:19 ` Avri Altman
2019-11-04 12:57 ` Avri Altman
2019-11-05 16:17 ` Alim Akhtar
2019-11-06 4:09 ` Alim Akhtar
2019-11-06 4:45 ` Bart Van Assche [this message]
2019-11-06 5:04 ` Martin K. Petersen
2019-11-05 5:01 ` 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=5dd9deb7-77c7-332c-6001-c6d232fa7f0d@acm.org \
--to=bvanassche@acm.org \
--cc=Avri.Altman@wdc.com \
--cc=alim.akhtar@gmail.com \
--cc=alim.akhtar@samsung.com \
--cc=hch@lst.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=kwmad.kim@samsung.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.