| Message ID | CAK8P3a0RDZpLtWjMEU1QVWSjOoqRAH6QxQ+ZQnJc8LwaV7m+JQ@mail.gmail.com |
|---|---|
| Headers | show |
| Series | SoC changes for 5.17 | expand |
Hi Arnd, Olof, On 12/23/2021 13:31, Arnd Bergmann wrote: > I'm sending out the pull requests for 5.17 early, as I won't have access to > my workstation for the next two weeks. With only 760 non-merge commits, > this again feels quieter than the massive previous merge window, but the > number of changed lines was actually slightly higher. > > There are very few changes aside from devicetree patches, most of > which are for the i.MX, Tegra, Qualcomm, Apple, K3 and Aspeed > platforms. > > We have a couple of new SoCs in existing families: > > - Qualcomm Snapdragon 8 Gen1 > - Qualcomm Snapdragon SDX65 > - NXP i.MX8ULP > - Texas Instruments j721s2 > - Renesas R-Car S4-8 > > The time between product announcement and kernel support is fairly short > for all of these, which is nice. In particular the two Snapdragons were only > announced this month and are the current high end of Qualcomm's products. > On the other end of the spectrum, we also add support for ST SPEAr320s, > which was launched 10 years ago. > > Aside from the Arm chips, there is also a pull request for a new RISC-V SoC, > the Starfive JH7100, including some of the basic drivers to make it boot. There seems to half of the submitted Broadcom SoCs pull request missing in this one, was there issues with those below: defconfigs: https://lore.kernel.org/linux-arm-kernel/20211221220642.2862218-1-f.fainelli@gmail.com/ https://lore.kernel.org/linux-arm-kernel/20211221220642.2862218-2-f.fainelli@gmail.com/ drivers: https://lore.kernel.org/linux-arm-kernel/20211221220642.2862218-5-f.fainelli@gmail.com/ Should I resend or fix something in those? Thanks! Happy holidays!
On 12/24/21 9:11 AM, Florian Fainelli wrote: > Hi Arnd, Olof, > > On 12/23/2021 13:31, Arnd Bergmann wrote: >> I'm sending out the pull requests for 5.17 early, as I won't have >> access to >> my workstation for the next two weeks. With only 760 non-merge commits, >> this again feels quieter than the massive previous merge window, but the >> number of changed lines was actually slightly higher. >> >> There are very few changes aside from devicetree patches, most of >> which are for the i.MX, Tegra, Qualcomm, Apple, K3 and Aspeed >> platforms. >> >> We have a couple of new SoCs in existing families: >> >> - Qualcomm Snapdragon 8 Gen1 >> - Qualcomm Snapdragon SDX65 >> - NXP i.MX8ULP >> - Texas Instruments j721s2 >> - Renesas R-Car S4-8 >> >> The time between product announcement and kernel support is fairly short >> for all of these, which is nice. In particular the two Snapdragons >> were only >> announced this month and are the current high end of Qualcomm's products. >> On the other end of the spectrum, we also add support for ST SPEAr320s, >> which was launched 10 years ago. >> >> Aside from the Arm chips, there is also a pull request for a new >> RISC-V SoC, >> the Starfive JH7100, including some of the basic drivers to make it boot. > > There seems to half of the submitted Broadcom SoCs pull request missing > in this one, was there issues with those below: > > defconfigs: > > https://lore.kernel.org/linux-arm-kernel/20211221220642.2862218-1-f.fainelli@gmail.com/ > > https://lore.kernel.org/linux-arm-kernel/20211221220642.2862218-2-f.fainelli@gmail.com/ > > > drivers: > > https://lore.kernel.org/linux-arm-kernel/20211221220642.2862218-5-f.fainelli@gmail.com/ > > > Should I resend or fix something in those? Thanks! Arnd, Olof, do I need to resend the 3 pull requests mentioned above? Thanks and happy new year.
Hi Florian, On Tue, Jan 4, 2022 at 1:58 PM Florian Fainelli <f.fainelli@gmail.com> wrote: > > On 12/24/21 9:11 AM, Florian Fainelli wrote: > > Hi Arnd, Olof, > > > > On 12/23/2021 13:31, Arnd Bergmann wrote: > >> I'm sending out the pull requests for 5.17 early, as I won't have > >> access to > >> my workstation for the next two weeks. With only 760 non-merge commits, > >> this again feels quieter than the massive previous merge window, but the > >> number of changed lines was actually slightly higher. > >> > >> There are very few changes aside from devicetree patches, most of > >> which are for the i.MX, Tegra, Qualcomm, Apple, K3 and Aspeed > >> platforms. > >> > >> We have a couple of new SoCs in existing families: > >> > >> - Qualcomm Snapdragon 8 Gen1 > >> - Qualcomm Snapdragon SDX65 > >> - NXP i.MX8ULP > >> - Texas Instruments j721s2 > >> - Renesas R-Car S4-8 > >> > >> The time between product announcement and kernel support is fairly short > >> for all of these, which is nice. In particular the two Snapdragons > >> were only > >> announced this month and are the current high end of Qualcomm's products. > >> On the other end of the spectrum, we also add support for ST SPEAr320s, > >> which was launched 10 years ago. > >> > >> Aside from the Arm chips, there is also a pull request for a new > >> RISC-V SoC, > >> the Starfive JH7100, including some of the basic drivers to make it boot. > > > > There seems to half of the submitted Broadcom SoCs pull request missing > > in this one, was there issues with those below: > > > > defconfigs: > > > > https://lore.kernel.org/linux-arm-kernel/20211221220642.2862218-1-f.fainelli@gmail.com/ > > > > https://lore.kernel.org/linux-arm-kernel/20211221220642.2862218-2-f.fainelli@gmail.com/ > > > > > > drivers: > > > > https://lore.kernel.org/linux-arm-kernel/20211221220642.2862218-5-f.fainelli@gmail.com/ > > > > > > Should I resend or fix something in those? Thanks! > > > Arnd, Olof, do I need to resend the 3 pull requests mentioned above? > Thanks and happy new year. I'm about to make a pass of merges, likely tomorrow -- I had to get my Honeycomb working again since it hosts all the trees and mailboxes for me. No need to resend at this time. -Olof
On Tue, Jan 4, 2022 at 7:40 PM Olof Johansson <olof@lixom.net> wrote: > On Tue, Jan 4, 2022 at 1:58 PM Florian Fainelli <f.fainelli@gmail.com> wrote: > > On 12/24/21 9:11 AM, Florian Fainelli wrote: > > > > > > Should I resend or fix something in those? Thanks! > > > > > > Arnd, Olof, do I need to resend the 3 pull requests mentioned above? > > Thanks and happy new year. > > I'm about to make a pass of merges, likely tomorrow -- I had to get my > Honeycomb working again since it hosts all the trees and mailboxes for > me. > > No need to resend at this time. It's possible that I had accidentally merged them in the end but tagged the branch without those merge commits, so have a look if it's in there. I'm still traveling, so I have no access to my reflog. I'm sure there was nothing wrong with the contents, so either they came after I had tagged the branches, or I made a mistake. Arnd
On Tue, Jan 4, 2022 at 5:40 PM Arnd Bergmann <arnd@kernel.org> wrote: > > On Tue, Jan 4, 2022 at 7:40 PM Olof Johansson <olof@lixom.net> wrote: > > On Tue, Jan 4, 2022 at 1:58 PM Florian Fainelli <f.fainelli@gmail.com> wrote: > > > On 12/24/21 9:11 AM, Florian Fainelli wrote: > > > > > > > > Should I resend or fix something in those? Thanks! > > > > > > > > > Arnd, Olof, do I need to resend the 3 pull requests mentioned above? > > > Thanks and happy new year. > > > > I'm about to make a pass of merges, likely tomorrow -- I had to get my > > Honeycomb working again since it hosts all the trees and mailboxes for > > me. > > > > No need to resend at this time. > > It's possible that I had accidentally merged them in the end but tagged > the branch without those merge commits, so have a look if it's in there. Yeah, it looks like there were a few merges not part of the pull request (Linus just merged them, so these showed up in regen-contents). I'll fold them into arm/late. arm/defconfig broadcom/defconfig [sign: Y Arnd Bergmann <arnd@arndb.de>] https://github.com/Broadcom/stblinux tags/arm-soc/for-5.17/defconfig broadcom/defconfig64 [sign: Y Arnd Bergmann <arnd@arndb.de>] https://github.com/Broadcom/stblinux tags/arm-soc/for-5.17/defconfig-arm64 qcom/defconfig [sign: N ] git://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux tags/qcom-arm64-defconfig-for-5.17 patch ARM: multi_v7_defconfig: Enable drivers for DragonBoard 410c [sign: N ] -Olof
On 1/10/22 10:32 AM, Olof Johansson wrote: > On Tue, Jan 4, 2022 at 5:40 PM Arnd Bergmann <arnd@kernel.org> wrote: >> >> On Tue, Jan 4, 2022 at 7:40 PM Olof Johansson <olof@lixom.net> wrote: >>> On Tue, Jan 4, 2022 at 1:58 PM Florian Fainelli <f.fainelli@gmail.com> wrote: >>>> On 12/24/21 9:11 AM, Florian Fainelli wrote: >>>>> >>>>> Should I resend or fix something in those? Thanks! >>>> >>>> >>>> Arnd, Olof, do I need to resend the 3 pull requests mentioned above? >>>> Thanks and happy new year. >>> >>> I'm about to make a pass of merges, likely tomorrow -- I had to get my >>> Honeycomb working again since it hosts all the trees and mailboxes for >>> me. >>> >>> No need to resend at this time. >> >> It's possible that I had accidentally merged them in the end but tagged >> the branch without those merge commits, so have a look if it's in there. > > Yeah, it looks like there were a few merges not part of the pull > request (Linus just merged them, so these showed up in > regen-contents). I'll fold them into arm/late. Thanks!
On Mon, Jan 10, 2022 at 12:34 PM Olof Johansson <olof@lixom.net> wrote: > > On Tue, Jan 4, 2022 at 5:40 PM Arnd Bergmann <arnd@kernel.org> wrote: > > > > On Tue, Jan 4, 2022 at 7:40 PM Olof Johansson <olof@lixom.net> wrote: > > > On Tue, Jan 4, 2022 at 1:58 PM Florian Fainelli <f.fainelli@gmail.com> wrote: > > > > On 12/24/21 9:11 AM, Florian Fainelli wrote: > > > > > > > > > > Should I resend or fix something in those? Thanks! > > > > > > > > > > > > Arnd, Olof, do I need to resend the 3 pull requests mentioned above? > > > > Thanks and happy new year. > > > > > > I'm about to make a pass of merges, likely tomorrow -- I had to get my > > > Honeycomb working again since it hosts all the trees and mailboxes for > > > me. > > > > > > No need to resend at this time. > > > > It's possible that I had accidentally merged them in the end but tagged > > the branch without those merge commits, so have a look if it's in there. > > Yeah, it looks like there were a few merges not part of the pull > request (Linus just merged them, so these showed up in > regen-contents). I'll fold them into arm/late. > It seems these (at the last the qcom ones) didn't make it into v5.17-rc1? Are you planning to pick up the qcom patches for v5.18 or should I just carry them and include them as I send my next PR? Regards, Bjorn > arm/defconfig > broadcom/defconfig [sign: Y Arnd Bergmann <arnd@arndb.de>] > https://github.com/Broadcom/stblinux > tags/arm-soc/for-5.17/defconfig > broadcom/defconfig64 [sign: Y Arnd Bergmann <arnd@arndb.de>] > https://github.com/Broadcom/stblinux > tags/arm-soc/for-5.17/defconfig-arm64 > qcom/defconfig [sign: N ] > > git://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux > tags/qcom-arm64-defconfig-for-5.17 > patch > ARM: multi_v7_defconfig: Enable drivers for > DragonBoard 410c [sign: N ] > > > -Olof > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
I'm sending out the pull requests for 5.17 early, as I won't have access to my workstation for the next two weeks. With only 760 non-merge commits, this again feels quieter than the massive previous merge window, but the number of changed lines was actually slightly higher. There are very few changes aside from devicetree patches, most of which are for the i.MX, Tegra, Qualcomm, Apple, K3 and Aspeed platforms. We have a couple of new SoCs in existing families: - Qualcomm Snapdragon 8 Gen1 - Qualcomm Snapdragon SDX65 - NXP i.MX8ULP - Texas Instruments j721s2 - Renesas R-Car S4-8 The time between product announcement and kernel support is fairly short for all of these, which is nice. In particular the two Snapdragons were only announced this month and are the current high end of Qualcomm's products. On the other end of the spectrum, we also add support for ST SPEAr320s, which was launched 10 years ago. Aside from the Arm chips, there is also a pull request for a new RISC-V SoC, the Starfive JH7100, including some of the basic drivers to make it boot. Arnd Dirstat 0.2% Documentation/devicetree/bindings/arm/apple/ 0.5% Documentation/devicetree/bindings/arm/tegra/ 0.6% Documentation/devicetree/bindings/arm/ 0.3% Documentation/devicetree/bindings/clock/ 0.5% Documentation/devicetree/bindings/firmware/ 0.3% Documentation/devicetree/bindings/gpu/host1x/ 0.3% Documentation/devicetree/bindings/mailbox/ 0.2% Documentation/devicetree/bindings/media/ 0.2% Documentation/devicetree/bindings/misc/ 0.9% Documentation/devicetree/bindings/mmc/ 0.5% Documentation/devicetree/bindings/pinctrl/ 0.2% Documentation/devicetree/bindings/soc/samsung/ 0.2% Documentation/devicetree/bindings/soc/ 1.3% Documentation/devicetree/bindings/ 46.4% arch/arm/boot/dts/ 0.6% arch/arm/ 0.3% arch/arm64/boot/dts/allwinner/ 0.3% arch/arm64/boot/dts/amlogic/ 2.2% arch/arm64/boot/dts/apple/ 11.7% arch/arm64/boot/dts/freescale/ 0.7% arch/arm64/boot/dts/mediatek/ 2.6% arch/arm64/boot/dts/nvidia/ 7.9% arch/arm64/boot/dts/qcom/ 1.6% arch/arm64/boot/dts/renesas/ 0.3% arch/arm64/boot/dts/rockchip/ 3.9% arch/arm64/boot/dts/ti/ 0.4% arch/arm64/boot/dts/ 0.5% arch/riscv/boot/dts/starfive/ 1.5% drivers/clk/starfive/ 0.2% drivers/memory/ 2.3% drivers/pinctrl/ 0.2% drivers/reset/ 0.5% drivers/soc/apple/ 0.2% drivers/soc/imx/ 0.6% drivers/soc/qcom/ 1.5% drivers/soc/renesas/ 0.4% drivers/soc/samsung/ 0.4% drivers/soc/tegra/ 0.2% drivers/soc/xilinx/ 0.8% drivers/tee/optee/ 0.2% drivers/tee/ 0.6% drivers/ 1.2% include/dt-bindings/clock/ 0.6% include/dt-bindings/pinctrl/ 0.2% include/dt-bindings/reset/ 0.2% include/dt-bindings/ 718 files changed, 62620 insertions(+), 16020 deletions(-) Most active contributors out of 183 individuals: 83 Thierry Reding 42 Dmitry Osipenko 22 Hector Martin 20 Konrad Dybcio 17 Vinod Koul 17 Giulio Benetti 15 Adam Ford 14 Jernej Skrabec 13 Yoshihiro Shimoda 13 Emil Renner Berthing 13 Biju Das 12 Sam Protsenko 12 Lad Prabhakar 12 Dmitry Baryshkov 12 Arnd Bergmann 10 Geert Uytterhoeven 10 Alexander Stein