From: Bart Van Assche <bvanassche@acm.org>
To: Avri Altman <Avri.Altman@wdc.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Daejun Park <daejun7.park@samsung.com>
Subject: Re: [PATCH v2] scsi: ufs: Use pre-calculated offsets in ufshcd_init_lrb
Date: Tue, 1 Oct 2024 10:19:14 -0700 [thread overview]
Message-ID: <2291e38f-1482-47f2-9c23-dfd259f53824@acm.org> (raw)
In-Reply-To: <DM6PR04MB6575B4ADD2F9E4A9DC80C81EFC772@DM6PR04MB6575.namprd04.prod.outlook.com>
On 10/1/24 12:19 AM, Avri Altman wrote:
> Bart - How do you want to proceed with this fix?
Since this patch affects the Exynos UFSHCI, I think we need feedback
from the maintainers of the Exynos UFSHCI code.
Personally I'm hesitant to proceed with this patch. As you may know the
android-mainline kernel tracks the upstream kernel very closely.
Currently that kernel branch is only one week behind Linus' master
branch. The android-mainline kernel boots fine on Pixel 6 devices. These
devices have an Exynos UFS host controller. Since this patch modifies
the behavior for the Exynos UFS host controller there is a potential
that it will break the support for that controller.
Thanks,
Bart.
next prev parent reply other threads:[~2024-10-01 17:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 4:45 [PATCH v2] scsi: ufs: Use pre-calculated offsets in ufshcd_init_lrb Avri Altman
2024-09-11 22:32 ` Bart Van Assche
2024-09-12 6:56 ` Avri Altman
2024-09-17 7:10 ` Avri Altman
2024-09-17 18:21 ` Bart Van Assche
2024-09-21 6:30 ` Avri Altman
2024-10-01 7:19 ` Avri Altman
2024-10-01 17:19 ` Bart Van Assche [this message]
2024-10-02 23:25 ` Bart Van Assche
2024-10-04 2:08 ` 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=2291e38f-1482-47f2-9c23-dfd259f53824@acm.org \
--to=bvanassche@acm.org \
--cc=Avri.Altman@wdc.com \
--cc=alim.akhtar@samsung.com \
--cc=daejun7.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=stable@vger.kernel.org \
/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