From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-arm-msm@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org,
Amit Pundir <amit.pundir@linaro.org>,
Luca Weiss <luca.weiss@fairphone.com>,
Brian Masney <bmasney@redhat.com>
Subject: Re: [PATCH v2] ufs: qcom: drop custom Android boot parameters
Date: Tue, 29 Mar 2022 23:59:41 -0400 [thread overview]
Message-ID: <yq1h77gt7j0.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20220321151853.24138-1-krzk@kernel.org> (Krzysztof Kozlowski's message of "Mon, 21 Mar 2022 16:18:53 +0100")
Krzysztof,
> The QCOM UFS driver requires an androidboot.bootdevice command line
> argument matching the UFS device name. If the name is different, it
> refuses to probe. This androidboot.bootdevice is provided by
> stock/vendor (from an Android-based device) bootloader.
Applied to 5.18/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2022-03-30 4:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220321151913epcas5p45ad53c827e3c87633acd29443322d0b5@epcas5p4.samsung.com>
2022-03-21 15:18 ` [PATCH v2] ufs: qcom: drop custom Android boot parameters Krzysztof Kozlowski
2022-03-21 15:40 ` Alim Akhtar
2022-03-22 18:14 ` 'Krzysztof Kozlowski'
2022-03-30 3:59 ` Martin K. Petersen [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=yq1h77gt7j0.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=agross@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=amit.pundir@linaro.org \
--cc=avri.altman@wdc.com \
--cc=bjorn.andersson@linaro.org \
--cc=bmasney@redhat.com \
--cc=jejb@linux.ibm.com \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=luca.weiss@fairphone.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;
as well as URLs for NNTP newsgroup(s).