From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Nitin Rawat <quic_nitirawa@quicinc.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Vinod Koul <vkoul@kernel.org>, <kishon@kernel.org>,
<manivannan.sadhasivam@linaro.org>,
<James.Bottomley@HansenPartnership.com>, <bvanassche@acm.org>,
<andersson@kernel.org>, <neil.armstrong@linaro.org>,
<konrad.dybcio@oss.qualcomm.com>,
<dmitry.baryshkov@oss.qualcomm.com>, <quic_rdwivedi@quicinc.com>,
<quic_cang@quicinc.com>, <linux-arm-msm@vger.kernel.org>,
<linux-phy@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<linux-scsi@vger.kernel.org>
Subject: Re: [PATCH V6 00/10] Refactor ufs phy powerup sequence
Date: Mon, 09 Jun 2025 21:44:43 -0400 [thread overview]
Message-ID: <yq1cybc74lw.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <c2b9dfbf-9163-4df5-bd0d-25c5bb43cfb5@quicinc.com> (Nitin Rawat's message of "Wed, 4 Jun 2025 13:07:15 +0530")
Nitin,
> For the remaining patches (Patch 2 - Patch 10), since Patch 2 (SCSI
> Patch) depends on PHY patches, can these patches be merged through the
> PHY tree?
Fine with me.
Acked-by: Martin K. Petersen <martin.petersen@oracle.com>
--
Martin K. Petersen
next prev parent reply other threads:[~2025-06-10 1:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 15:38 Nitin Rawat
2025-05-26 15:38 ` [PATCH V6 01/10] scsi: ufs: qcom: Prevent calling phy_exit before phy_init Nitin Rawat
2025-06-22 19:23 ` Abel Vesa
2025-05-26 15:38 ` [PATCH V6 02/10] scsi: ufs: qcom: add a new phy calibrate API call Nitin Rawat
2025-06-22 19:24 ` Abel Vesa
2025-05-26 15:38 ` [PATCH V6 03/10] phy: qcom-qmp-ufs: Rename qmp_ufs_enable and qmp_ufs_power_on Nitin Rawat
2025-05-26 15:38 ` [PATCH V6 04/10] phy: qcom-qmp-ufs: Refactor phy_power_on and phy_calibrate callbacks Nitin Rawat
2025-05-26 15:38 ` [PATCH V6 05/10] phy: qcom-qmp-ufs: Refactor UFS PHY reset Nitin Rawat
2025-05-26 15:38 ` [PATCH V6 06/10] phy: qcom-qmp-ufs: Remove qmp_ufs_com_init() Nitin Rawat
2025-05-26 15:38 ` [PATCH V6 07/10] phy: qcom-qmp-ufs: Rename qmp_ufs_power_off Nitin Rawat
2025-05-26 15:38 ` [PATCH V6 08/10] phy: qcom-qmp-ufs: Remove qmp_ufs_exit() and Inline qmp_ufs_com_exit() Nitin Rawat
2025-05-26 15:38 ` [PATCH V6 09/10] phy: qcom-qmp-ufs: refactor qmp_ufs_power_off Nitin Rawat
2025-05-26 15:38 ` [PATCH V6 10/10] scsi: ufs: qcom : Refactor phy_power_on/off calls Nitin Rawat
2025-06-19 13:53 ` Aishwarya
2025-06-20 14:25 ` Nitin Rawat
2025-06-20 21:44 ` Aishwarya
2025-06-21 17:15 ` Nitin Rawat
[not found] ` <CGME20250626072554eucas1p2ae35c30a96ab1ca61b6a3d6a970708ee@eucas1p2.samsung.com>
2025-06-26 7:25 ` Marek Szyprowski
2025-05-28 2:15 ` [PATCH V6 00/10] Refactor ufs phy powerup sequence Martin K. Petersen
2025-06-04 7:37 ` Nitin Rawat
2025-06-10 1:44 ` Martin K. Petersen [this message]
2025-06-15 16:52 ` (subset) " Vinod Koul
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=yq1cybc74lw.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=andersson@kernel.org \
--cc=bvanassche@acm.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=kishon@kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_cang@quicinc.com \
--cc=quic_nitirawa@quicinc.com \
--cc=quic_rdwivedi@quicinc.com \
--cc=vkoul@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
all inboxes | Powered by JetHome®