From: Krzysztof Kozlowski <krzk@kernel.org>
To: Matt Ranostay <mranostay@ti.com>
Cc: bhelgaas@google.com, robh+dt@kernel.org, kishon@ti.com,
vigneshr@ti.com, linux-pci@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 0/2] dt-bindings: PCI: ti,j721e-pci-*: resolve unexpected property warnings
Date: Mon, 26 Sep 2022 08:18:43 +0200 [thread overview]
Message-ID: <d36585af-1706-2499-3ccc-c61a2cd49be4@kernel.org> (raw)
In-Reply-To: <YzEXN88AAa7tZvyE@ubuntu>
On 26/09/2022 05:06, Matt Ranostay wrote:
> On Sun, Sep 25, 2022 at 11:21:02AM +0200, Krzysztof Kozlowski wrote:
>> On 25/09/2022 00:35, Matt Ranostay wrote:
>>> Resolve unexpected property warnings related to interrupts in both J721E PCI EP and host
>>> yaml files.
>>>
>>
>> Thanks for cc-ing. On what tree do you base your patch? Looks like
>> something old. If so, you need to rebase to some recent kernel.
>>
>
> It was on linux-next from Sep 23rd. So would seem odd if the rebasing seems
> from an older tree.
That's good, but then why you did not use scripts/get_maintainers.pl as
I asked...
Best regards,
Krzysztof
prev parent reply other threads:[~2022-09-26 6:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-24 22:35 [PATCH v2 0/2] dt-bindings: PCI: ti,j721e-pci-*: resolve unexpected property warnings Matt Ranostay
2022-09-24 22:35 ` [PATCH v2 1/2] dt-bindings: PCI: ti,j721e-pci-host: add interrupt controller definition Matt Ranostay
2022-09-29 20:11 ` Rob Herring
2022-09-24 22:35 ` [PATCH v2 2/2] dt-bindings: PCI: ti,j721e-pci-*: Add missing interrupt properties Matt Ranostay
2022-09-29 20:12 ` Rob Herring
2022-09-25 9:21 ` [PATCH v2 0/2] dt-bindings: PCI: ti,j721e-pci-*: resolve unexpected property warnings Krzysztof Kozlowski
2022-09-26 3:06 ` Matt Ranostay
2022-09-26 6:18 ` Krzysztof Kozlowski [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=d36585af-1706-2499-3ccc-c61a2cd49be4@kernel.org \
--to=krzk@kernel.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-pci@vger.kernel.org \
--cc=mranostay@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.com \
/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