lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 13 Jan 2023 15:23:18 +0100
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     Bjorn Helgaas <helgaas@...nel.org>
Cc:     Lorenzo Pieralisi <lpieralisi@...nel.org>,
        Andy Gross <agross@...nel.org>, linux-arm-msm@...r.kernel.org,
        Bjorn Helgaas <bhelgaas@...gle.com>,
        linux-kernel@...r.kernel.org,
        Manivannan Sadhasivam <mani@...nel.org>,
        linux-pci@...r.kernel.org,
        Konrad Dybcio <konrad.dybcio@...aro.org>,
        Rob Herring <robh+dt@...nel.org>,
        Bjorn Andersson <andersson@...nel.org>,
        devicetree@...r.kernel.org,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
        Rob Herring <robh@...nel.org>
Subject: Re: [PATCH v2] dt-bindings: PCI: qcom,pcie-ep: correct
 qcom,perst-regs

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.

Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ