From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Nitin Rawat <quic_nitirawa@quicinc.com>,
Can Guo <quic_cang@quicinc.com>,
Naveen Kumar Goud Arepalli <quic_narepall@quicinc.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
Bart Van Assche <bvanassche@acm.org>,
Andy Gross <agross@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-scsi@vger.kernel.org,
devicetree@vger.kernel.org, stable@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v3 0/5] scsi: ufs: qcom: fix UFSDHCD support on MSM8996 platform
Date: Mon, 26 Feb 2024 21:33:04 -0500 [thread overview]
Message-ID: <yq1o7c24oyt.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20240218-msm8996-fix-ufs-v3-0-40aab49899a3@linaro.org> (Dmitry Baryshkov's message of "Sun, 18 Feb 2024 15:56:33 +0200")
Dmitry,
> First several patches target fixing the UFS support on the Qualcomm
> MSM8996 / APQ8096 platforms, broken by the commit b4e13e1ae95e ("scsi:
> ufs: qcom: Add multiple frequency support for
> MAX_CORE_CLK_1US_CYCLES"). Last two patches clean up the UFS DT device
> on that platform to follow the bindings on other MSM8969 platforms. If
> such breaking change is unacceptable, they can be simply ignored,
> merging fixes only.
Does not apply to 6.9/scsi-staging. Please rebase if you want this
series to go through the SCSI tree.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2024-02-27 2:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-18 13:56 [PATCH v3 0/5] scsi: ufs: qcom: fix UFSDHCD support on MSM8996 platform Dmitry Baryshkov
2024-02-18 13:56 ` [PATCH v3 1/5] scsi: ufs: qcom: provide default cycles_in_1us value Dmitry Baryshkov
2024-02-18 13:56 ` [PATCH v3 2/5] arm64: dts: qcom: msm8996: specify UFS core_clk frequencies Dmitry Baryshkov
2024-02-18 13:56 ` [PATCH v3 3/5] arm64: dts: qcom: msm8996: set GCC_UFS_ICE_CORE_CLK freq directly Dmitry Baryshkov
2024-02-18 13:56 ` [PATCH v3 4/5] dt-bindings: ufs: qcom,ufs: drop source clock entries Dmitry Baryshkov
2024-02-18 13:56 ` [PATCH v3 5/5] arm64: dts: qcom: msm8996: drop source clock entries from the UFS node Dmitry Baryshkov
2024-02-27 2:33 ` Martin K. Petersen [this message]
2024-02-28 13:02 ` [PATCH v3 0/5] scsi: ufs: qcom: fix UFSDHCD support on MSM8996 platform Dmitry Baryshkov
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=yq1o7c24oyt.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=agross@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=andersson@kernel.org \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=jejb@linux.ibm.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=quic_cang@quicinc.com \
--cc=quic_narepall@quicinc.com \
--cc=quic_nitirawa@quicinc.com \
--cc=robh@kernel.org \
--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 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.