From: Tommaso Merciai <tomm.merciai@gmail.com>
To: nicolas saenz julienne <nsaenz@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: bcm2711-rpi-4-b: Fix pcie0, pci warning.
Date: Mon, 27 Sep 2021 00:33:15 +0200 [thread overview]
Message-ID: <20210926223315.GA39851@tom-desktop> (raw)
In-Reply-To: <408e5e27fae24f22a408afdaf538702858cc324c.camel@kernel.org>
On Mon, Sep 20, 2021 at 10:21:46AM +0200, nicolas saenz julienne wrote:
> Hi Tommaso,
>
> On Sat, 2021-09-18 at 16:35 +0200, Tommaso Merciai wrote:
> > Fix the following warning:
> >
> > ./scripts/dtc/include-prefixes/arm/bcm2711-rpi-4-b.dts:220.10-231.4:
> > Warning (pci_device_reg):
> > /scb/pcie@7d500000/pci@1,0: PCI unit address format error, expected "0,0"
> >
> > Signed-off-by: Tommaso Merciai <tomm.merciai@gmail.com>
> > ---
>
> This issue was already addressed here:
> https://lore.kernel.org/all/20210831125843.1233488-2-nsaenzju@redhat.com/
>
> It's available in linux-next and will eventually show up upstream.
>
> Regards,
> Nicolas
>
Hi Nicolas,
Thanks for your feedback.
Tommaso
WARNING: multiple messages have this Message-ID (diff)
From: Tommaso Merciai <tomm.merciai@gmail.com>
To: nicolas saenz julienne <nsaenz@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: bcm2711-rpi-4-b: Fix pcie0, pci warning.
Date: Mon, 27 Sep 2021 00:33:15 +0200 [thread overview]
Message-ID: <20210926223315.GA39851@tom-desktop> (raw)
In-Reply-To: <408e5e27fae24f22a408afdaf538702858cc324c.camel@kernel.org>
On Mon, Sep 20, 2021 at 10:21:46AM +0200, nicolas saenz julienne wrote:
> Hi Tommaso,
>
> On Sat, 2021-09-18 at 16:35 +0200, Tommaso Merciai wrote:
> > Fix the following warning:
> >
> > ./scripts/dtc/include-prefixes/arm/bcm2711-rpi-4-b.dts:220.10-231.4:
> > Warning (pci_device_reg):
> > /scb/pcie@7d500000/pci@1,0: PCI unit address format error, expected "0,0"
> >
> > Signed-off-by: Tommaso Merciai <tomm.merciai@gmail.com>
> > ---
>
> This issue was already addressed here:
> https://lore.kernel.org/all/20210831125843.1233488-2-nsaenzju@redhat.com/
>
> It's available in linux-next and will eventually show up upstream.
>
> Regards,
> Nicolas
>
Hi Nicolas,
Thanks for your feedback.
Tommaso
_______________________________________________
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-09-26 22:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-18 14:35 [PATCH] ARM: dts: bcm2711-rpi-4-b: Fix pcie0, pci warning Tommaso Merciai
2021-09-18 14:35 ` Tommaso Merciai
2021-09-20 8:21 ` nicolas saenz julienne
2021-09-20 8:21 ` nicolas saenz julienne
2021-09-26 22:33 ` Tommaso Merciai [this message]
2021-09-26 22:33 ` Tommaso Merciai
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=20210926223315.GA39851@tom-desktop \
--to=tomm.merciai@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=nsaenz@kernel.org \
--cc=robh+dt@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.