From: Marc Zyngier <maz@kernel.org>
To: "Pali Rohár" <pali@kernel.org>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
luca@lucaceresoli.net, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org,
kernel-team@android.com, alyssa@rosenzweig.io,
lorenzo.pieralisi@arm.com, bhelgaas@google.com,
joey.gouly@arm.com
Subject: Re: [PATCH v2] PCI: apple: Follow the PCIe specifications when resetting the port
Date: Tue, 23 Nov 2021 13:09:02 +0000 [thread overview]
Message-ID: <87ilwjc93l.wl-maz@kernel.org> (raw)
In-Reply-To: <20211123122719.lput7rmn7qr5wkrj@pali>
On Tue, 23 Nov 2021 12:27:19 +0000,
Pali Rohár <pali@kernel.org> wrote:
>
> U-Boot has its own copy of DTS files, right? So it can be fixed in
> U-Boot driver together with U-Boot DTS file at the same time.
No, there is only a single DTS, solely provided by either u-boot or
the earlier firmware. The version in the kernel tree is purely for
documentation purposes.
M.
--
Without deviation from the norm, progress is not possible.
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: "Pali Rohár" <pali@kernel.org>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
luca@lucaceresoli.net, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org,
kernel-team@android.com, alyssa@rosenzweig.io,
lorenzo.pieralisi@arm.com, bhelgaas@google.com,
joey.gouly@arm.com
Subject: Re: [PATCH v2] PCI: apple: Follow the PCIe specifications when resetting the port
Date: Tue, 23 Nov 2021 13:09:02 +0000 [thread overview]
Message-ID: <87ilwjc93l.wl-maz@kernel.org> (raw)
In-Reply-To: <20211123122719.lput7rmn7qr5wkrj@pali>
On Tue, 23 Nov 2021 12:27:19 +0000,
Pali Rohár <pali@kernel.org> wrote:
>
> U-Boot has its own copy of DTS files, right? So it can be fixed in
> U-Boot driver together with U-Boot DTS file at the same time.
No, there is only a single DTS, solely provided by either u-boot or
the earlier firmware. The version in the kernel tree is purely for
documentation purposes.
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-11-23 13:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 10:41 [PATCH v2] PCI: apple: Follow the PCIe specifications when resetting the port Marc Zyngier
2021-11-22 10:41 ` Marc Zyngier
2021-11-22 12:03 ` Pali Rohár
2021-11-22 12:03 ` Pali Rohár
2021-11-22 14:43 ` Marc Zyngier
2021-11-22 14:43 ` Marc Zyngier
2021-11-22 21:32 ` Luca Ceresoli
2021-11-22 21:32 ` Luca Ceresoli
2021-11-23 8:48 ` Marc Zyngier
2021-11-23 8:48 ` Marc Zyngier
2021-11-23 12:27 ` Mark Kettenis
2021-11-23 12:27 ` Mark Kettenis
2021-11-22 21:50 ` Mark Kettenis
2021-11-22 21:50 ` Mark Kettenis
2021-11-23 12:24 ` Marc Zyngier
2021-11-23 12:24 ` Marc Zyngier
2021-11-23 12:27 ` Pali Rohár
2021-11-23 12:27 ` Pali Rohár
2021-11-23 13:09 ` Marc Zyngier [this message]
2021-11-23 13:09 ` Marc Zyngier
2021-11-23 12:49 ` Mark Kettenis
2021-11-23 12:49 ` Mark Kettenis
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=87ilwjc93l.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=alyssa@rosenzweig.io \
--cc=bhelgaas@google.com \
--cc=joey.gouly@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=luca@lucaceresoli.net \
--cc=mark.kettenis@xs4all.nl \
--cc=pali@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.