From: Florian Fainelli <florian.fainelli@broadcom.com> To: soc@kernel.org Cc: Stefan Wahren <wahrenst@gmx.net>, Florian Fainelli <florian.fainelli@broadcom.com>, linux-arm-kernel@lists.infradead.org, arnd@arndb.de, olof@lixom.net, khilman@kernel.org, bcm-kernel-feedback-list@broadcom.com Subject: [GIT PULL 1/1] Broadcom devicetree fixes for 6.7 Date: Tue, 5 Dec 2023 14:50:21 -0800 [thread overview] Message-ID: <20231205225021.653045-1-florian.fainelli@broadcom.com> (raw) The following changes since commit b85ea95d086471afb4ad062012a4d73cd328fa86: Linux 6.7-rc1 (2023-11-12 16:19:07 -0800) are available in the Git repository at: https://github.com/Broadcom/stblinux.git tags/arm-soc/for-6.7/devicetree-fixes for you to fetch changes up to dc761f11af2e39119d3a7942e3d10615f3d900e7: ARM: dts: bcm2711-rpi-400: Fix delete-node of led_act (2023-11-28 16:26:07 -0800) ---------------------------------------------------------------- This pull request contains Broadcom ARM-based SoCs Device Tree fixes for 6.7, please pull the following: - Stefan corrects the disabling of the activity LED for the Raspberry Pi 400 ---------------------------------------------------------------- Stefan Wahren (1): ARM: dts: bcm2711-rpi-400: Fix delete-node of led_act arch/arm/boot/dts/broadcom/bcm2711-rpi-400.dts | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Florian Fainelli <florian.fainelli@broadcom.com> To: soc@kernel.org Cc: Stefan Wahren <wahrenst@gmx.net>, Florian Fainelli <florian.fainelli@broadcom.com>, linux-arm-kernel@lists.infradead.org, arnd@arndb.de, olof@lixom.net, khilman@kernel.org, bcm-kernel-feedback-list@broadcom.com Subject: [GIT PULL 1/1] Broadcom devicetree fixes for 6.7 Date: Tue, 5 Dec 2023 14:50:21 -0800 [thread overview] Message-ID: <20231205225021.653045-1-florian.fainelli@broadcom.com> (raw) The following changes since commit b85ea95d086471afb4ad062012a4d73cd328fa86: Linux 6.7-rc1 (2023-11-12 16:19:07 -0800) are available in the Git repository at: https://github.com/Broadcom/stblinux.git tags/arm-soc/for-6.7/devicetree-fixes for you to fetch changes up to dc761f11af2e39119d3a7942e3d10615f3d900e7: ARM: dts: bcm2711-rpi-400: Fix delete-node of led_act (2023-11-28 16:26:07 -0800) ---------------------------------------------------------------- This pull request contains Broadcom ARM-based SoCs Device Tree fixes for 6.7, please pull the following: - Stefan corrects the disabling of the activity LED for the Raspberry Pi 400 ---------------------------------------------------------------- Stefan Wahren (1): ARM: dts: bcm2711-rpi-400: Fix delete-node of led_act arch/arm/boot/dts/broadcom/bcm2711-rpi-400.dts | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-12-05 22:50 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-05 22:50 Florian Fainelli [this message] 2023-12-05 22:50 ` [GIT PULL 1/1] Broadcom devicetree fixes for 6.7 Florian Fainelli 2023-12-06 16:19 ` patchwork-bot+linux-soc
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=20231205225021.653045-1-florian.fainelli@broadcom.com \ --to=florian.fainelli@broadcom.com \ --cc=arnd@arndb.de \ --cc=bcm-kernel-feedback-list@broadcom.com \ --cc=khilman@kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=olof@lixom.net \ --cc=soc@kernel.org \ --cc=wahrenst@gmx.net \ /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: linkBe 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.