Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	andersson@kernel.org, lpieralisi@kernel.org, kw@linux.com,
	krzysztof.kozlowski+dt@linaro.org, robh@kernel.org
Cc: konrad.dybcio@linaro.org, linux-arm-msm@vger.kernel.org,
	devicetree@vger.kernel.org, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org, quic_srichara@quicinc.com
Subject: Re: [PATCH v4 14/18] dt-bindings: PCI: qcom: Add "mhi" register region to supported SoCs
Date: Thu, 16 Mar 2023 08:58:56 +0100	[thread overview]
Message-ID: <1b0c4e5b-55e6-e519-bff1-a641e0141a8b@linaro.org> (raw)
In-Reply-To: <20230315064255.15591-15-manivannan.sadhasivam@linaro.org>

On 15/03/2023 07:42, Manivannan Sadhasivam wrote:
> "mhi" register region contains the MHI registers that could be used by
> the PCIe controller drivers to get debug information like PCIe link
> transition counts on newer SoCs.
> 
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>

This is a friendly reminder during the review process.

It looks like you received a tag and forgot to add it.

If you do not know the process, here is a short explanation:
Please add Acked-by/Reviewed-by/Tested-by tags when posting new
versions. However, there's no need to repost patches *only* to add the
tags. The upstream maintainer will do that for acks received on the
version they apply.

https://elixir.bootlin.com/linux/v5.17/source/Documentation/process/submitting-patches.rst#L540

If a tag was not added on purpose, please state why and what changed.


Best regards,
Krzysztof


  reply	other threads:[~2023-03-16  7:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15  6:42 [PATCH v4 00/18] Qcom PCIe cleanups and improvements Manivannan Sadhasivam
2023-03-15  6:42 ` [PATCH v4 01/18] PCI: qcom: Remove PCIE20_ prefix from register definitions Manivannan Sadhasivam
2023-03-15  6:42 ` [PATCH v4 02/18] PCI: qcom: Sort and group registers and bitfield definitions Manivannan Sadhasivam
2023-03-15  6:42 ` [PATCH v4 03/18] PCI: qcom: Use bitfield definitions for register fields Manivannan Sadhasivam
2023-03-15  6:42 ` [PATCH v4 04/18] PCI: qcom: Add missing macros " Manivannan Sadhasivam
2023-03-15  6:42 ` [PATCH v4 05/18] PCI: qcom: Use lower case for hex Manivannan Sadhasivam
2023-03-15 10:34   ` Konrad Dybcio
2023-03-15 13:31     ` Manivannan Sadhasivam
2023-03-15  6:42 ` [PATCH v4 06/18] PCI: qcom: Use bulk reset APIs for handling resets for IP rev 2.1.0 Manivannan Sadhasivam
2023-03-15  6:42 ` [PATCH v4 07/18] PCI: qcom: Use bulk clock APIs for handling clocks for IP rev 1.0.0 Manivannan Sadhasivam
2023-03-15  6:42 ` [PATCH v4 08/18] PCI: qcom: Use bulk clock APIs for handling clocks for IP rev 2.3.2 Manivannan Sadhasivam
2023-03-15  6:42 ` [PATCH v4 09/18] PCI: qcom: Use bulk clock APIs for handling clocks for IP rev 2.3.3 Manivannan Sadhasivam
2023-03-15  6:42 ` [PATCH v4 10/18] PCI: qcom: Use bulk reset APIs for handling resets " Manivannan Sadhasivam
2023-03-15  6:42 ` [PATCH v4 11/18] PCI: qcom: Use bulk reset APIs for handling resets for IP rev 2.4.0 Manivannan Sadhasivam
2023-03-15  6:42 ` [PATCH v4 12/18] PCI: qcom: Use macros for defining total no. of clocks & supplies Manivannan Sadhasivam
2023-03-15  6:42 ` [PATCH v4 13/18] PCI: qcom: Rename qcom_pcie_config_sid_sm8250() to reflect IP version Manivannan Sadhasivam
2023-03-15  6:42 ` [PATCH v4 14/18] dt-bindings: PCI: qcom: Add "mhi" register region to supported SoCs Manivannan Sadhasivam
2023-03-16  7:58   ` Krzysztof Kozlowski [this message]
2023-03-15  6:42 ` [PATCH v4 15/18] arm64: dts: qcom: sdm845: Add "mhi" region to the PCIe nodes Manivannan Sadhasivam
2023-03-15  6:42 ` [PATCH v4 16/18] arm64: dts: qcom: sm8250: " Manivannan Sadhasivam
2023-03-15  6:42 ` [PATCH v4 17/18] arm64: dts: qcom: sc8280xp: " Manivannan Sadhasivam
2023-03-15  6:42 ` [PATCH v4 18/18] PCI: qcom: Expose link transition counts via debugfs Manivannan Sadhasivam

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=1b0c4e5b-55e6-e519-bff1-a641e0141a8b@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=andersson@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kw@linux.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=quic_srichara@quicinc.com \
    --cc=robh@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