Re: [PATCH v2] dt-bindings: PCI: qcom,pcie-ep: correct qcom,perst-regs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Jan 13, 2023 at 03:23:18PM +0100, Krzysztof Kozlowski wrote:
> On 13/01/2023 15:03, Bjorn Helgaas wrote:
> > On Fri, Jan 13, 2023 at 10:02:27AM +0100, Krzysztof Kozlowski wrote:
> >> 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?
> > 
> > It's on Lorenzo's branch
> > (https://git.kernel.org/pub/scm/linux/kernel/git/lpieralisi/pci.git/)
> > but I haven't pulled it into my "next" branch yet.  Will try to do
> > that today.
> 
> If Lorenzo picks up patches which at some point are merged by another
> maintainer, his tree should be in linux-next as well (and in LKP tests).
> Otherwise we loose some build and test coverage.

Oh, I remember what happened.  I started the merge a while ago and
tripped over the conflict between these:

  dt-bindings: PCI: qcom: add MSM8998 specific compatible
  dt-bindings: PCI: qcom: Add sm8350 to bindings

I asked about splitting the first and if you did that, I missed it,
and in the meantime I got distracted by my E820/EfiMemoryMappedIO
regression.

In any event, I updated "next" with this.  Check my conflict
resolution because I'm not a DT expert:

https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/tree/Documentation/devicetree/bindings/pci/qcom,pcie.yaml?id=25cfdd48a4bd



[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux