[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f277507b-b62e-c874-b2ad-276ea03d2263@acm.org>
Date: Mon, 13 Sep 2021 20:23:01 -0700
From: Bart Van Assche <bvanassche@....org>
To: Alim Akhtar <alim.akhtar@...il.com>
Cc: Kiwoong Kim <kwmad.kim@...sung.com>, linux-scsi@...r.kernel.org,
open list <linux-kernel@...r.kernel.org>,
Alim Akhtar <alim.akhtar@...sung.com>,
Avri Altman <avri.altman@....com>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
"Bean Huo (beanhuo)" <beanhuo@...ron.com>,
Can Guo <cang@...eaurora.org>,
Adrian Hunter <adrian.hunter@...el.com>, sc.suh@...sung.com,
hy50.seo@...sung.com, sh425.lee@...sung.com,
bhoon95.kim@...sung.com
Subject: Re: [PATCH v2 0/3] scsi: ufs: introduce vendor isr
On 9/13/21 10:26, Alim Akhtar wrote:
> Thanks for your input. Completely agree with you, in fact your
> suggestions make sense to me. As a driver developer, surely we can
> take these concerns to the IP designers and see how far we can get in
> terms of standardization. That, however, is not something that can be
> accomplished overnight. My main concern is, what about millions of
> devices which are already in the market? UFS subsystem does support
> _vops_ to handle vendor specific hooks/modifications. I am not saying
> we should always follow this path, but surely until these deviations
> are either fixed or become part of UFS standard itself, IMO.
Hi Alim,
If there are already millions of devices in the market that support this
feature then that's an argument to proceed with this patch series.
Thanks,
Bart.
Powered by blists - more mailing lists