All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avri Altman <Avri.Altman@wdc.com>
To: Avri Altman <Avri.Altman@wdc.com>,
	"James E . J . Bottomley" <jejb@linux.ibm.com>,
	"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: "hch@infradead.org" <hch@infradead.org>,
	Bart Van Assche <bvanassche@acm.org>,
	Bean Huo <beanhuo@micron.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v2 0/1] Remove support for legacy UFS
Date: Wed, 3 Apr 2024 11:48:26 +0000	[thread overview]
Message-ID: <DM6PR04MB6575D506E6E426B8B57F3C2DFC3D2@DM6PR04MB6575.namprd04.prod.outlook.com> (raw)
In-Reply-To: <20240327071714.757-1-avri.altman@wdc.com>

Martin hi,
Could you please take a look at this?
I have another cleanup series pending.

Thanks,
Avri

> UFS1.0 and UFS1.1, published in the early 2010s, were more of a proof of
> concept rather than a mature functional spec. Toshiba was the only
> device manufacturer with the most accomplished phy team to come up with
> a small UFS1.0 device. Alas, there were no commercial platforms it can
> be paired with. Even UFS2.0 that was published in 2013, didn't really
> make it to the market: too moot to take effect. It's not until UFS2.1
> that was published in 2016, were a myriad of devices and platforms
> flooded the market. Designated to mobile devices, dictates a rapid short
> lives for those platforms. Hence, we can safely remove those pre-UFS2.1
> pieces of code.
> 
> Changes from v1:
>  - remove ufshcd_get_local_unipro_ver which practically mean squashing
>    patch 1 & 2 into a single patch (Christoph)
>  - restore an if clause to avoid functional change in
>    ufshcd_compl_one_cqe (Bart)
> 
> 
> Avri Altman (1):
>   scsi: ufs: Remove support for old UFSHCI versions
> 
>  drivers/ufs/core/ufshcd.c   | 174 +++---------------------------------
>  drivers/ufs/host/ufs-qcom.c |   3 +-
>  include/ufs/ufshcd.h        |   2 -
>  include/ufs/ufshci.h        |   7 --
>  4 files changed, 15 insertions(+), 171 deletions(-)
> 
> --
> 2.42.0


      parent reply	other threads:[~2024-04-03 11:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-27  7:17 [PATCH v2 0/1] Remove support for legacy UFS Avri Altman
2024-03-27  7:17 ` [PATCH v2 1/1] scsi: ufs: Remove support for old UFSHCI versions Avri Altman
2024-04-03 16:26   ` Bart Van Assche
2024-04-03 19:24     ` Avri Altman
2024-04-03 21:17       ` Bart Van Assche
2024-04-04  7:22         ` Avri Altman
2024-04-04  8:45   ` Bean Huo
2024-04-05  8:11   ` Bean Huo
2024-04-03 11:48 ` Avri Altman [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=DM6PR04MB6575D506E6E426B8B57F3C2DFC3D2@DM6PR04MB6575.namprd04.prod.outlook.com \
    --to=avri.altman@wdc.com \
    --cc=beanhuo@micron.com \
    --cc=bvanassche@acm.org \
    --cc=hch@infradead.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 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.