From: Florian Fainelli <f.fainelli@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>, devicetree@vger.kernel.org
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Rob Herring <robh+dt@kernel.org>, Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
"maintainer:BROADCOM IPROC ARM ARCHITECTURE"
<bcm-kernel-feedback-list@broadcom.com>,
"open list:PCI SUBSYSTEM" <linux-pci@vger.kernel.org>,
"moderated list:BROADCOM IPROC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 0/6] Convert iProc PCIe binding to YAML
Date: Mon, 13 Dec 2021 10:44:58 -0800 [thread overview]
Message-ID: <7d44fec0-bbbd-c15e-9d60-1a0ecd962045@gmail.com> (raw)
In-Reply-To: <20211210200451.3849106-1-f.fainelli@gmail.com>
On 12/10/21 12:04 PM, Florian Fainelli wrote:
> This patch series converts the iProc PCIe binding to YAML. Given there
> is a majority of DTS changes, it would make sense for me to pull this
> via the Broadcom ARM SoC git tree.
>
> Thanks!
>
> Changes in v4:
This is not what I did in this version, I will send a v5. Sorry about
the noise.
--
Florian
prev parent reply other threads:[~2021-12-13 18:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 20:04 [PATCH v4 0/6] Convert iProc PCIe binding to YAML Florian Fainelli
2021-12-10 20:04 ` [PATCH v4 1/6] ARM: dts: Cygnus: Fixed iProc PCIe controller properties Florian Fainelli
2021-12-10 20:04 ` [PATCH v4 2/6] ARM: dts: Cygnus: Update PCIe PHY node unit name(s) Florian Fainelli
2021-12-10 20:04 ` [PATCH v4 3/6] ARM: dts: HR2: Fixed iProc PCIe MSI sub-node Florian Fainelli
2021-12-10 20:04 ` [PATCH v4 4/6] ARM: dts: NSP: " Florian Fainelli
2021-12-10 20:04 ` [PATCH v4 5/6] dt-bindings: phy: Convert Cygnus PCIe PHY to YAML Florian Fainelli
2021-12-10 20:04 ` [PATCH v4 6/6] dt-bindings: pci: Convert iProc PCIe " Florian Fainelli
2021-12-13 18:44 ` Florian Fainelli [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=7d44fec0-bbbd-c15e-9d60-1a0ecd962045@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.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;
as well as URLs for NNTP newsgroup(s).