From: Bart Van Assche <bvanassche@acm.org>
To: "Bean Huo" <beanhuo@iokpp.de>,
"Fang Hongjie(方洪杰)" <hongjiefang@asrmicro.com>,
"alim.akhtar@samsung.com" <alim.akhtar@samsung.com>,
"avri.altman@wdc.com" <avri.altman@wdc.com>,
"James.Bottomley@HansenPartnership.com"
<James.Bottomley@HansenPartnership.com>,
"martin.petersen@oracle.com" <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>
Subject: Re: [PATCH v5] scsi: ufs: core: call hibern8 notify when hibern8 cmd failed
Date: Wed, 6 May 2026 11:16:06 +0200 [thread overview]
Message-ID: <619d81fe-1db1-41b6-b9b2-a2546a030881@acm.org> (raw)
In-Reply-To: <a349ab70dbed9355785bec38c7e05658f3c948a6.camel@iokpp.de>
On 5/6/26 10:47 AM, Bean Huo wrote:
> Thanks for the explanation. However, the kernel development practice is to not
> merge infrastructure without at least one in-tree user. Please resubmit this
> patch together with your platform driver (or at least the hibern8_notify
> callback that handles ROLLBACK_CHANGE) so reviewers can verify the design is
> correct and actually works as intended.
>
> @Bart, any idea?
Everyone who works on Android smartphones has to deal with the following:
- The upstream-first policy.
- Not disclosing any aspect of the phone under development until it has
been announced publicly.
Typically two years elapse between the start of testing kernel code for
a new phone and public announcement. Another 1 - 4 years elapse after
a phone has been announced until all kernel code for a smartphone is
upstream. Insisting on not merging any code upstream until a user for
the code is upstream makes the job of smartphone kernel developers
harder than necessary.
This is why I'm fine with deviating from the rule explained in your
email for small changes.
Thanks,
Bart.
next prev parent reply other threads:[~2026-05-06 9:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-02 14:30 [PATCH v5] scsi: ufs: core: call hibern8 notify when hibern8 cmd failed Hongjie Fang
2026-05-04 2:30 ` Bart Van Assche
2026-05-05 6:40 ` Bean Huo
2026-05-06 3:29 ` Fang Hongjie(方洪杰)
2026-05-06 8:47 ` Bean Huo
2026-05-06 9:16 ` Bart Van Assche [this message]
2026-05-06 12:43 ` Bean Huo
2026-05-07 12:06 ` Fang Hongjie(方洪杰)
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=619d81fe-1db1-41b6-b9b2-a2546a030881@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@iokpp.de \
--cc=hongjiefang@asrmicro.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