From: Linus Walleij <linus.walleij@linaro.org>
To: Corentin Labbe <clabbe@baylibre.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Rob Herring <robh+dt@kernel.org>,
Hans Ulli Kroll <ulli.kroll@googlemail.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-pci <linux-pci@vger.kernel.org>
Subject: Re: [PATCH 2/2] ARM: dts: gemini: add device_type on pci
Date: Thu, 6 May 2021 12:34:06 +0200 [thread overview]
Message-ID: <CACRpkdYZQcbJju_t-tVv2+uGQaf9MUCoAE4YXPNoLW1R2mMWQw@mail.gmail.com> (raw)
In-Reply-To: <20210503185228.1518131-2-clabbe@baylibre.com>
On Mon, May 3, 2021 at 8:52 PM Corentin Labbe <clabbe@baylibre.com> wrote:
> Fixes DT warning on pci node by adding the missing device_type.
>
> Signed-off-by: Corentin Labbe <clabbe@baylibre.com>
Thanks, patch applied!
This is even required for port-mapped IO-space to work
I think, but nothing uses that so that's why I didn't notice.
Yours,
Linus Walleij
WARNING: multiple messages have this Message-ID (diff)
From: Linus Walleij <linus.walleij@linaro.org>
To: Corentin Labbe <clabbe@baylibre.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Rob Herring <robh+dt@kernel.org>,
Hans Ulli Kroll <ulli.kroll@googlemail.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-pci <linux-pci@vger.kernel.org>
Subject: Re: [PATCH 2/2] ARM: dts: gemini: add device_type on pci
Date: Thu, 6 May 2021 12:34:06 +0200 [thread overview]
Message-ID: <CACRpkdYZQcbJju_t-tVv2+uGQaf9MUCoAE4YXPNoLW1R2mMWQw@mail.gmail.com> (raw)
In-Reply-To: <20210503185228.1518131-2-clabbe@baylibre.com>
On Mon, May 3, 2021 at 8:52 PM Corentin Labbe <clabbe@baylibre.com> wrote:
> Fixes DT warning on pci node by adding the missing device_type.
>
> Signed-off-by: Corentin Labbe <clabbe@baylibre.com>
Thanks, patch applied!
This is even required for port-mapped IO-space to work
I think, but nothing uses that so that's why I didn't notice.
Yours,
Linus Walleij
_______________________________________________
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-05-06 10:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 18:52 [PATCH 1/2] dt-bindings: pci: convert faraday,ftpci100 to yaml Corentin Labbe
2021-05-03 18:52 ` Corentin Labbe
2021-05-03 18:52 ` [PATCH 2/2] ARM: dts: gemini: add device_type on pci Corentin Labbe
2021-05-03 18:52 ` Corentin Labbe
2021-05-06 10:34 ` Linus Walleij [this message]
2021-05-06 10:34 ` Linus Walleij
2021-05-06 10:32 ` [PATCH 1/2] dt-bindings: pci: convert faraday,ftpci100 to yaml Linus Walleij
2021-05-06 10:32 ` Linus Walleij
2021-05-06 17:43 ` Rob Herring
2021-05-06 17:43 ` Rob Herring
2021-05-06 20:34 ` Bjorn Helgaas
2021-05-06 20:34 ` Bjorn Helgaas
2021-05-07 10:51 ` Linus Walleij
2021-05-07 10:51 ` Linus Walleij
2021-05-10 18:35 ` Bjorn Helgaas
2021-05-10 18:35 ` Bjorn Helgaas
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=CACRpkdYZQcbJju_t-tVv2+uGQaf9MUCoAE4YXPNoLW1R2mMWQw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=bhelgaas@google.com \
--cc=clabbe@baylibre.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=robh+dt@kernel.org \
--cc=ulli.kroll@googlemail.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 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.