From: Thierry Reding <treding@nvidia.com>
To: Rob Herring <robh@kernel.org>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Bjorn Helgaas" <helgaas@kernel.org>,
"Vidya Sagar" <vidyas@nvidia.com>,
"Serge Semin" <Sergey.Semin@baikalelectronics.ru>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Krzysztof Wilczyński" <kw@linux.com>
Subject: Re: [GIT PULL] PCI changes for v6.2
Date: Thu, 15 Dec 2022 13:11:43 +0100 [thread overview]
Message-ID: <Y5sO/1klSvVCyWNz@orome> (raw)
In-Reply-To: <CAL_Jsq+Y1CN4BMhB-FXFunr1rFs62QEMi_zj3zmvjXrksCQ0sA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1511 bytes --]
On Wed, Dec 14, 2022 at 06:22:27PM -0600, Rob Herring wrote:
> On Wed, Dec 14, 2022 at 12:01 PM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > On Tue, Dec 13, 2022 at 3:30 PM Bjorn Helgaas <helgaas@kernel.org> wrote:
> > >
> > > You will see a merge conflict in
> > > Documentation/devicetree/bindings/pci/snps,dw-pcie.yaml between these:
> > >
> > > 5c3741492d2e ("dt-bindings: PCI: tegra234: Add ECAM support")
> > > 4cc13eedb892 ("dt-bindings: PCI: dwc: Add reg/reg-names common properties")
> > >
> > > 5c3741492d2e is already in your tree via arm-soc, and 4cc13eedb892 is in
> > > this pull request. The resolution I suggest is to use 4cc13eedb892, which
> > > means we'll lose the addition of "ecam" from 5c3741492d2e.
> >
> > Heh. I only read this part once I had already resolved that thing differently.
> >
> > I dunno, I used my own - possibly bad - judgment to add a case for
> > that 'ecam' thing under the vendor-specific list.
> >
> > That was very much a "monkey see, monkey do" resolution, so some DT
> > person should check it out and possibly make fun of me and my dubious
> > ancestry. Rob? Thierry?
>
> Good job writing valid json-schema! :) It's close enough and better
> than just dropping which caused warnings. It is Tegra only ATM, but
> anyone else that sets up an ECAM region should use the same name.
Yeah, seems fine as-is for now. We can always move this out of the
vendor-specific list once others start using it.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-12-15 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 23:30 [GIT PULL] PCI changes for v6.2 Bjorn Helgaas
2022-12-14 18:01 ` Linus Torvalds
2022-12-15 0:22 ` Rob Herring
2022-12-15 12:11 ` Thierry Reding [this message]
2022-12-14 18:04 ` pr-tracker-bot
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=Y5sO/1klSvVCyWNz@orome \
--to=treding@nvidia.com \
--cc=Sergey.Semin@baikalelectronics.ru \
--cc=helgaas@kernel.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=robh@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vidyas@nvidia.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