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: Christoph Hellwig <hch@infradead.org>,
Bart Van Assche <bvanassche@acm.org>,
Bean Huo <beanhuo@micron.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] scsi: ufs: Remove support for old UFSHCI versions
Date: Thu, 04 Apr 2024 10:45:23 +0200 [thread overview]
Message-ID: <535d994d8498daee40fda2d044cefeeda33ac38b.camel@gmail.com> (raw)
In-Reply-To: <20240327071714.757-2-avri.altman@wdc.com>
On Wed, 2024-03-27 at 09:17 +0200, Avri Altman wrote:
> UFS spec version 2.1 was published more than 10 years ago. It is
> vanishingly unlikely that even there are out there platforms that
> uses
> earlier host controllers, let alone that those ancient platforms will
> ever run a V6.10 kernel. Thus, remove support of host controllers
> prior
> to UFS2.1.
>
> This patch removes some legacy tuning calls that no longer apply.
>
> Signed-off-by: Avri Altman <avri.altman@wdc.com>
Hi Avri,
I think it's safe to remove support for UFS versions < UFS 2.1, but not
100% sure, let me check and give you a solid answer then.
Bean
next prev parent reply other threads:[~2024-04-04 8:45 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 [this message]
2024-04-05 8:11 ` Bean Huo
2024-04-03 11:48 ` [PATCH v2 0/1] Remove support for legacy UFS Avri Altman
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=535d994d8498daee40fda2d044cefeeda33ac38b.camel@gmail.com \
--to=huobean@gmail.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox