From: nicolas saenz julienne <nsaenz@kernel.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 2/3] bcm2835-dt-fixes-2021-12-13
Date: Sat, 18 Dec 2021 19:04:27 +0100 [thread overview]
Message-ID: <bbfb9c184aaf75536fb7bb8acf7ae35fe3c77545.camel@kernel.org> (raw)
In-Reply-To: <20211213123040.184359-2-nsaenzju@redhat.com>
On Mon, 2021-12-13 at 13:30 +0100, Nicolas Saenz Julienne wrote:
> Hi Florian,
>
> The following changes since commit fa55b7dcdc43c1aa1ba12bca9d2dd4318c2a0dbf:
>
> Linux 5.16-rc1 (2021-11-14 13:56:52 -0800)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/nsaenz/linux-rpi.git tags/bcm2835-dt-fixes-2021-12-13
>
> for you to fetch changes up to 6a56599b5a6b19adb21f8f0d9f2d33511426fb20:
>
> ARM: dts: gpio-ranges property is now required (2021-12-13 13:06:25 +0100)
>
> ----------------------------------------------------------------
> A series of devicetree fixes aimed at the Raspberry Pi family of boards:
>
> - Phil Elwell adds gpio-ranges to RPi's main GPIO/PINCTRL driver
> - Phil Elwell and Stefan Wahren correct RPi400's GPIO expander's
> labels
> - Stefan Wahren drops fallback compatible from RPi2's vchiq devicetree
> node
>
> ----------------------------------------------------------------
> Phil Elwell (2):
> ARM: dts: bcm2711-rpi-400: Fix GPIO expander labels
Hi Florian,
I know you're in the loop, but just to be safe. Both patches below are no
longer needed: the gpio-ranges change was applied by linusw alongside its
pinctrl counterpart, vchiq's fallback will remain as is.
> ARM: dts: gpio-ranges property is now required
> ARM: dts: bcm283x: Drop fallback compatible for vchiq
If it makes your life simpler I can send a second 'dt-fixes' pull request.
Regards,
Nicolas
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: nicolas saenz julienne <nsaenz@kernel.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 2/3] bcm2835-dt-fixes-2021-12-13
Date: Sat, 18 Dec 2021 19:04:27 +0100 [thread overview]
Message-ID: <bbfb9c184aaf75536fb7bb8acf7ae35fe3c77545.camel@kernel.org> (raw)
In-Reply-To: <20211213123040.184359-2-nsaenzju@redhat.com>
On Mon, 2021-12-13 at 13:30 +0100, Nicolas Saenz Julienne wrote:
> Hi Florian,
>
> The following changes since commit fa55b7dcdc43c1aa1ba12bca9d2dd4318c2a0dbf:
>
> Linux 5.16-rc1 (2021-11-14 13:56:52 -0800)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/nsaenz/linux-rpi.git tags/bcm2835-dt-fixes-2021-12-13
>
> for you to fetch changes up to 6a56599b5a6b19adb21f8f0d9f2d33511426fb20:
>
> ARM: dts: gpio-ranges property is now required (2021-12-13 13:06:25 +0100)
>
> ----------------------------------------------------------------
> A series of devicetree fixes aimed at the Raspberry Pi family of boards:
>
> - Phil Elwell adds gpio-ranges to RPi's main GPIO/PINCTRL driver
> - Phil Elwell and Stefan Wahren correct RPi400's GPIO expander's
> labels
> - Stefan Wahren drops fallback compatible from RPi2's vchiq devicetree
> node
>
> ----------------------------------------------------------------
> Phil Elwell (2):
> ARM: dts: bcm2711-rpi-400: Fix GPIO expander labels
Hi Florian,
I know you're in the loop, but just to be safe. Both patches below are no
longer needed: the gpio-ranges change was applied by linusw alongside its
pinctrl counterpart, vchiq's fallback will remain as is.
> ARM: dts: gpio-ranges property is now required
> ARM: dts: bcm283x: Drop fallback compatible for vchiq
If it makes your life simpler I can send a second 'dt-fixes' pull request.
Regards,
Nicolas
next prev parent reply other threads:[~2021-12-18 18:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 12:30 [GIT PULL 1/3] bcm2835-dt-next-2021-12-13 Nicolas Saenz Julienne
2021-12-13 12:30 ` Nicolas Saenz Julienne
2021-12-13 12:30 ` [GIT PULL 2/3] bcm2835-dt-fixes-2021-12-13 Nicolas Saenz Julienne
2021-12-13 12:30 ` Nicolas Saenz Julienne
2021-12-14 3:37 ` Florian Fainelli
2021-12-14 3:37 ` Florian Fainelli
2021-12-18 18:04 ` nicolas saenz julienne [this message]
2021-12-18 18:04 ` nicolas saenz julienne
2021-12-13 12:30 ` [GIT PULL 3/3] bcm2835-bindings-2021-12-13 Nicolas Saenz Julienne
2021-12-13 12:30 ` Nicolas Saenz Julienne
2021-12-14 3:38 ` Florian Fainelli
2021-12-14 3:38 ` Florian Fainelli
2021-12-18 16:34 ` Florian Fainelli
2021-12-18 16:34 ` Florian Fainelli
2021-12-18 16:38 ` Nicolas Saenz Julienne
2021-12-18 16:38 ` Nicolas Saenz Julienne
2021-12-14 3:38 ` [GIT PULL 1/3] bcm2835-dt-next-2021-12-13 Florian Fainelli
2021-12-14 3:38 ` Florian Fainelli
2021-12-14 7:31 ` Nicolas Saenz Julienne
2021-12-14 7:31 ` Nicolas Saenz Julienne
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=bbfb9c184aaf75536fb7bb8acf7ae35fe3c77545.camel@kernel.org \
--to=nsaenz@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=nsaenzjulienne@suse.de \
/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.