From: Vinod Koul <vkoul@kernel.org>
To: Johan Hovold <johan+linaro@kernel.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 00/11] phy: qcom-qmp: more fixes and cleanups (set 1)
Date: Mon, 17 Oct 2022 13:45:57 +0530 [thread overview]
Message-ID: <Y00PPSxezyr+WhY3@matsya> (raw)
In-Reply-To: <20221017065013.19647-1-johan+linaro@kernel.org>
On 17-10-22, 08:50, Johan Hovold wrote:
> Here's the next batch of QMP driver fixes and cleanups.
>
> Dmitry suggested that the register layout structs could all be using
> per-IP version defines, which in principle sounds like a good idea. It
> is a separate change though, and one which would require some more work
> as it is not always clear which IP version a specific SoC uses (e.g.
> some of the IPQ platforms appear to mix and match currently).
>
> As such a change shouldn't block these clean ups, I've dropped the
> merging of the IPQ SDM845 PCIe layout structs in v2.
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2022-10-17 8:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 6:50 [PATCH v3 00/11] phy: qcom-qmp: more fixes and cleanups (set 1) Johan Hovold
2022-10-17 6:50 ` [PATCH v3 01/11] phy: qcom-qmp: fix obsolete lane comments Johan Hovold
2022-10-17 6:50 ` [PATCH v3 02/11] phy: qcom-qmp-combo: drop unused UFS reset Johan Hovold
2022-10-17 6:50 ` [PATCH v3 03/11] phy: qcom-qmp-pcie: drop unused common-block registers Johan Hovold
2022-10-17 6:50 ` [PATCH v3 04/11] phy: qcom-qmp-pcie: clean up power-down handling Johan Hovold
2022-10-17 6:50 ` [PATCH v3 05/11] phy: qcom-qmp-pcie: move power-down update Johan Hovold
2022-10-17 6:50 ` [PATCH v3 06/11] phy: qcom-qmp-pcie-msm8996: clean up power-down handling Johan Hovold
2022-10-17 6:50 ` [PATCH v3 07/11] phy: qcom-qmp-combo: " Johan Hovold
2022-10-17 6:50 ` [PATCH v3 08/11] phy: qcom-qmp-ufs: " Johan Hovold
2022-10-17 6:50 ` [PATCH v3 09/11] phy: qcom-qmp-usb: " Johan Hovold
2022-10-17 6:50 ` [PATCH v3 10/11] phy: qcom-qmp-pcie: clean up clock lists Johan Hovold
2022-10-17 6:50 ` [PATCH v3 11/11] phy: qcom-qmp-pcie: drop bogus register update Johan Hovold
2022-10-17 8:15 ` Vinod Koul [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=Y00PPSxezyr+WhY3@matsya \
--to=vkoul@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=johan+linaro@kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.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