| Message ID | 20220721000626.29497-1-william.zhang@broadcom.com |
|---|---|
| Headers | show |
| Series | arm64: bcmbca: Move BCM4908 SoC support under ARCH_BCMBCA | expand |
On 7/20/2022 5:06 PM, William Zhang wrote: > RESEND to include linux arm kernel mailing list. > > Now that Broadcom Broadband arch ARCH_BCMBCA is in the kernel, this change > set migrates the existing broadband chip BCM4908 support to ARCH_BCMBCA. Looks like only 1, 2 4 and 5 made it to bcm-kernel-feedback-list meaning that our patchwork instance did not pick them all up. Did you use patman to send these patches? If so, you might still need to make sure that the final CC list includes the now (ex) BCM4908 maintainer and the ARM SoC maintainer for Broadcom changes.
On 7/20/2022 8:32 PM, Florian Fainelli wrote: > > > On 7/20/2022 5:06 PM, William Zhang wrote: >> RESEND to include linux arm kernel mailing list. >> >> Now that Broadcom Broadband arch ARCH_BCMBCA is in the kernel, this >> change >> set migrates the existing broadband chip BCM4908 support to ARCH_BCMBCA. > > Looks like only 1, 2 4 and 5 made it to bcm-kernel-feedback-list meaning > that our patchwork instance did not pick them all up. > > Did you use patman to send these patches? If so, you might still need to > make sure that the final CC list includes the now (ex) BCM4908 > maintainer and the ARM SoC maintainer for Broadcom changes. And the threading was broken because the patches 1-9 were not in response to your cover letter.
You know nobody understands a damn word of anything in this email. You can not do searches through email. Stop harassing me. Reporting y’all doesn’t work and I’m not deleting my account because of you. So stop fucking with me. Thanks Bye > On Jul 20, 2022, at 11:35 PM, Florian Fainelli <f.fainelli@gmail.com> wrote: > > > >> On 7/20/2022 8:32 PM, Florian Fainelli wrote: >>> On 7/20/2022 5:06 PM, William Zhang wrote: >>> RESEND to include linux arm kernel mailing list. >>> >>> Now that Broadcom Broadband arch ARCH_BCMBCA is in the kernel, this change >>> set migrates the existing broadband chip BCM4908 support to ARCH_BCMBCA. >> Looks like only 1, 2 4 and 5 made it to bcm-kernel-feedback-list meaning that our patchwork instance did not pick them all up. >> Did you use patman to send these patches? If so, you might still need to make sure that the final CC list includes the now (ex) BCM4908 maintainer and the ARM SoC maintainer for Broadcom changes. > > And the threading was broken because the patches 1-9 were not in response to your cover letter. > -- > Florian > > ______________________________________________________ > Linux MTD discussion mailing list > http://lists.infradead.org/mailman/listinfo/linux-mtd/
Stop fucking with me you pathetic idiots. > On Jul 20, 2022, at 11:46 PM, Vanessa Page <Vebpe@outlook.com> wrote: > > You know nobody understands a damn word of anything in this email. You can not do searches through email. Stop harassing me. Reporting y’all doesn’t work and I’m not deleting my account because of you. So stop fucking with me. > > Thanks > Bye > >> On Jul 20, 2022, at 11:35 PM, Florian Fainelli <f.fainelli@gmail.com> wrote: >> >> >> >>> On 7/20/2022 8:32 PM, Florian Fainelli wrote: >>>>> On 7/20/2022 5:06 PM, William Zhang wrote: >>>>> RESEND to include linux arm kernel mailing list. >>>>> >>>>> Now that Broadcom Broadband arch ARCH_BCMBCA is in the kernel, this change >>>>> set migrates the existing broadband chip BCM4908 support to ARCH_BCMBCA. >>> Looks like only 1, 2 4 and 5 made it to bcm-kernel-feedback-list meaning that our patchwork instance did not pick them all up. >>> Did you use patman to send these patches? If so, you might still need to make sure that the final CC list includes the now (ex) BCM4908 maintainer and the ARM SoC maintainer for Broadcom changes. >> >> And the threading was broken because the patches 1-9 were not in response to your cover letter. >> -- >> Florian >> >> ______________________________________________________ >> Linux MTD discussion mailing list >> http://lists.infradead.org/mailman/listinfo/linux-mtd/ > ______________________________________________________ > Linux MTD discussion mailing list > http://lists.infradead.org/mailman/listinfo/linux-mtd/
Your career is harassing peoples inboxes you stupid motherfuckers. > On Jul 20, 2022, at 11:46 PM, Vanessa Page <Vebpe@outlook.com> wrote: > > You know nobody understands a damn word of anything in this email. You can not do searches through email. Stop harassing me. Reporting y’all doesn’t work and I’m not deleting my account because of you. So stop fucking with me. > > Thanks > Bye > >> On Jul 20, 2022, at 11:35 PM, Florian Fainelli <f.fainelli@gmail.com> wrote: >> >> >> >>> On 7/20/2022 8:32 PM, Florian Fainelli wrote: >>>>> On 7/20/2022 5:06 PM, William Zhang wrote: >>>>> RESEND to include linux arm kernel mailing list. >>>>> >>>>> Now that Broadcom Broadband arch ARCH_BCMBCA is in the kernel, this change >>>>> set migrates the existing broadband chip BCM4908 support to ARCH_BCMBCA. >>> Looks like only 1, 2 4 and 5 made it to bcm-kernel-feedback-list meaning that our patchwork instance did not pick them all up. >>> Did you use patman to send these patches? If so, you might still need to make sure that the final CC list includes the now (ex) BCM4908 maintainer and the ARM SoC maintainer for Broadcom changes. >> >> And the threading was broken because the patches 1-9 were not in response to your cover letter. >> -- >> Florian >> >> ______________________________________________________ >> Linux MTD discussion mailing list >> http://lists.infradead.org/mailman/listinfo/linux-mtd/ > ______________________________________________________ > Linux MTD discussion mailing list > http://lists.infradead.org/mailman/listinfo/linux-mtd/
On 2022-07-21 02:06, William Zhang wrote: > RESEND to include linux arm kernel mailing list. > > Now that Broadcom Broadband arch ARCH_BCMBCA is in the kernel, this > change > set migrates the existing broadband chip BCM4908 support to > ARCH_BCMBCA. I'd expect me to receive patches 7/9, 8/9 and 9/9 too.
On 07/20/2022 11:55 PM, Rafał Miłecki wrote: > On 2022-07-21 02:06, William Zhang wrote: >> RESEND to include linux arm kernel mailing list. >> >> Now that Broadcom Broadband arch ARCH_BCMBCA is in the kernel, this >> change >> set migrates the existing broadband chip BCM4908 support to ARCH_BCMBCA. > > I'd expect me to receive patches 7/9, 8/9 and 9/9 too. I will explicitly add you to the cc list. The get_maintainer.pl does not return your email for these three patches. I guess it is because the MAINTAINER file does not have your name for 4908 ARCH. I
RESEND to include linux arm kernel mailing list. Now that Broadcom Broadband arch ARCH_BCMBCA is in the kernel, this change set migrates the existing broadband chip BCM4908 support to ARCH_BCMBCA. William Zhang (9): dt-bindings: arm64: bcmbca: Merge BCM4908 into BCMBCA dt-bindings: arm64: bcmbca: Update BCM4908 description arm64: dts: bcmbca: update BCM4908 board dts files arm64: dts: Move BCM4908 dts to bcmbca folder arm64: dts: Add BCM4908 generic board dts arm64: bcmbca: Make BCM4908 drivers depend on ARCH_BCMBCA arm64: bcmbca: Merge ARCH_BCM4908 to ARCH_BCMBCA MAINTAINERS: Add BCM4908 maintainer to BCMBCA entry arm64: defconfig: remove BCM4908 .../bindings/arm/bcm/brcm,bcm4908.yaml | 42 ------------------- .../bindings/arm/bcm/brcm,bcmbca.yaml | 25 +++++++++++ MAINTAINERS | 1 + arch/arm64/Kconfig.platforms | 10 +---- arch/arm64/boot/dts/broadcom/Makefile | 1 - arch/arm64/boot/dts/broadcom/bcm4908/Makefile | 5 --- arch/arm64/boot/dts/broadcom/bcmbca/Makefile | 5 +++ .../bcm4906-netgear-r8000p.dts | 2 +- .../bcm4906-tplink-archer-c2300-v1.dts | 2 +- .../broadcom/{bcm4908 => bcmbca}/bcm4906.dtsi | 0 .../bcm4908-asus-gt-ac5300.dts | 2 +- .../bcm4908-netgear-raxe500.dts | 2 +- .../broadcom/{bcm4908 => bcmbca}/bcm4908.dtsi | 0 .../boot/dts/broadcom/bcmbca/bcm94908.dts | 30 +++++++++++++ arch/arm64/configs/defconfig | 1 - drivers/i2c/busses/Kconfig | 4 +- drivers/mtd/parsers/Kconfig | 6 +-- drivers/net/ethernet/broadcom/Kconfig | 4 +- drivers/pci/controller/Kconfig | 2 +- drivers/phy/broadcom/Kconfig | 4 +- drivers/pinctrl/bcm/Kconfig | 4 +- drivers/reset/Kconfig | 2 +- drivers/soc/bcm/bcm63xx/Kconfig | 4 +- drivers/tty/serial/Kconfig | 4 +- drivers/watchdog/Kconfig | 2 +- 25 files changed, 84 insertions(+), 80 deletions(-) delete mode 100644 Documentation/devicetree/bindings/arm/bcm/brcm,bcm4908.yaml delete mode 100644 arch/arm64/boot/dts/broadcom/bcm4908/Makefile rename arch/arm64/boot/dts/broadcom/{bcm4908 => bcmbca}/bcm4906-netgear-r8000p.dts (96%) rename arch/arm64/boot/dts/broadcom/{bcm4908 => bcmbca}/bcm4906-tplink-archer-c2300-v1.dts (99%) rename arch/arm64/boot/dts/broadcom/{bcm4908 => bcmbca}/bcm4906.dtsi (100%) rename arch/arm64/boot/dts/broadcom/{bcm4908 => bcmbca}/bcm4908-asus-gt-ac5300.dts (97%) rename arch/arm64/boot/dts/broadcom/{bcm4908 => bcmbca}/bcm4908-netgear-raxe500.dts (89%) rename arch/arm64/boot/dts/broadcom/{bcm4908 => bcmbca}/bcm4908.dtsi (100%) create mode 100644 arch/arm64/boot/dts/broadcom/bcmbca/bcm94908.dts