From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Lorenzo Pieralisi <lpieralisi@kernel.org>,
Andy Gross <agross@kernel.org>,
linux-arm-msm@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
linux-kernel@vger.kernel.org,
Manivannan Sadhasivam <mani@kernel.org>,
linux-pci@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
devicetree@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v2] dt-bindings: PCI: qcom,pcie-ep: correct qcom,perst-regs
Date: Fri, 13 Jan 2023 10:02:27 +0100 [thread overview]
Message-ID: <7831a607-db55-274c-8fba-d01d5bac3a7a@linaro.org> (raw)
In-Reply-To: <167240770788.754221.16859969124148517946.b4-ty@kernel.org>
On 30/12/2022 14:42, Lorenzo Pieralisi wrote:
> On Wed, 9 Nov 2022 12:32:02 +0100, Krzysztof Kozlowski wrote:
>> qcom,perst-regs is an phandle array of one item with a phandle and its
>> arguments.
>>
>>
>
> Applied to pci/dt, thanks!
>
> [1/1] dt-bindings: PCI: qcom,pcie-ep: correct qcom,perst-regs
> https://git.kernel.org/lpieralisi/pci/c/68909a813609
It's still not in linux-next. Is you tree correctly included in the next?
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-01-13 9:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 11:32 [PATCH v2] dt-bindings: PCI: qcom,pcie-ep: correct qcom,perst-regs Krzysztof Kozlowski
2022-12-30 13:42 ` Lorenzo Pieralisi
2023-01-13 9:02 ` Krzysztof Kozlowski [this message]
2023-01-13 14:03 ` Bjorn Helgaas
2023-01-13 14:23 ` Krzysztof Kozlowski
2023-01-13 22:47 ` Bjorn Helgaas
2023-01-15 11:27 ` Krzysztof Kozlowski
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=7831a607-db55-274c-8fba-d01d5bac3a7a@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).