From: Florian Fainelli <f.fainelli@gmail.com> To: soc@kernel.org Cc: Florian Fainelli <f.fainelli@gmail.com>, William Zhang <william.zhang@broadcom.com>, Peter Robinson <pbrobinson@gmail.com>, Nicolas Saenz Julienne <nsaenz@kernel.org>, Stefan Wahren <stefan.wahren@i2se.com>, Javier Martinez Canillas <javierm@redhat.com>, linux-arm-kernel@lists.infradead.org, arnd@arndb.de, olof@lixom.net, khilman@kernel.org, bcm-kernel-feedback-list@broadcom.com Subject: [PATCH 0/7] Broadcom SoC updates for 5.20 Date: Mon, 11 Jul 2022 09:44:44 -0700 [thread overview] Message-ID: <20220711164451.3542127-1-f.fainelli@gmail.com> (raw) Hi Arnd, Olof, The highlights of the pull requests are: - William and Anand add support for a large number of Broadband Carrier Access (BCA) DSL/PON/Wi-Fi router chips under the ARCH_BCMBCA umbrella and we expect to see more activity in the future on these chips. - Peter, Nicolas and Stefan add support for the V3D GPU on the Raspberry Pi 4 (BCM2711) You will meet the following conflict which was identified in linux-next: https://lore.kernel.org/lkml/20220711095520.4fad4c97@canb.auug.org.au/ which can be resolved by removing arch/arm/mach-bcm/bcm63xx.c Thanks to these changes having soaked in linux-next for a couple of weeks, we do not expect other merge conflicts or problems. Thank you! -- 2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: Florian Fainelli <f.fainelli@gmail.com> To: soc@kernel.org Cc: Florian Fainelli <f.fainelli@gmail.com>, William Zhang <william.zhang@broadcom.com>, Peter Robinson <pbrobinson@gmail.com>, Nicolas Saenz Julienne <nsaenz@kernel.org>, Stefan Wahren <stefan.wahren@i2se.com>, Javier Martinez Canillas <javierm@redhat.com>, linux-arm-kernel@lists.infradead.org, arnd@arndb.de, olof@lixom.net, khilman@kernel.org, bcm-kernel-feedback-list@broadcom.com Subject: [PATCH 0/7] Broadcom SoC updates for 5.20 Date: Mon, 11 Jul 2022 09:44:44 -0700 [thread overview] Message-ID: <20220711164451.3542127-1-f.fainelli@gmail.com> (raw) Hi Arnd, Olof, The highlights of the pull requests are: - William and Anand add support for a large number of Broadband Carrier Access (BCA) DSL/PON/Wi-Fi router chips under the ARCH_BCMBCA umbrella and we expect to see more activity in the future on these chips. - Peter, Nicolas and Stefan add support for the V3D GPU on the Raspberry Pi 4 (BCM2711) You will meet the following conflict which was identified in linux-next: https://lore.kernel.org/lkml/20220711095520.4fad4c97@canb.auug.org.au/ which can be resolved by removing arch/arm/mach-bcm/bcm63xx.c Thanks to these changes having soaked in linux-next for a couple of weeks, we do not expect other merge conflicts or problems. Thank you! -- 2.25.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-07-11 16:45 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-11 16:44 Florian Fainelli [this message] 2022-07-11 16:44 ` [PATCH 0/7] Broadcom SoC updates for 5.20 Florian Fainelli 2022-07-11 16:44 ` [GIT PULL 1/7] Broadcom defconfig changes " Florian Fainelli 2022-07-11 16:44 ` Florian Fainelli 2022-07-11 16:44 ` [GIT PULL 2/7] Broadcom defconfig-arm64 " Florian Fainelli 2022-07-11 16:44 ` Florian Fainelli 2022-07-11 16:44 ` [GIT PULL 3/7] Broadcom devicetree " Florian Fainelli 2022-07-11 16:44 ` Florian Fainelli 2022-07-11 16:44 ` [GIT PULL 4/7] Broadcom devicetree-arm64 " Florian Fainelli 2022-07-11 16:44 ` Florian Fainelli 2022-07-11 16:44 ` [GIT PULL 5/7] Broadcom drivers " Florian Fainelli 2022-07-11 16:44 ` Florian Fainelli 2022-07-11 16:44 ` [GIT PULL 6/7] Broadcom maintainers " Florian Fainelli 2022-07-11 16:44 ` Florian Fainelli 2022-07-11 16:44 ` [GIT PULL 7/7] Broadcom soc " Florian Fainelli 2022-07-11 16:44 ` Florian Fainelli 2022-07-12 21:30 ` [PATCH 0/7] Broadcom SoC updates " patchwork-bot+linux-soc 2022-07-13 21:00 ` patchwork-bot+linux-soc 2022-07-14 16:10 ` 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=20220711164451.3542127-1-f.fainelli@gmail.com \ --to=f.fainelli@gmail.com \ --cc=arnd@arndb.de \ --cc=bcm-kernel-feedback-list@broadcom.com \ --cc=javierm@redhat.com \ --cc=khilman@kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=nsaenz@kernel.org \ --cc=olof@lixom.net \ --cc=pbrobinson@gmail.com \ --cc=soc@kernel.org \ --cc=stefan.wahren@i2se.com \ --cc=william.zhang@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: 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.