linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Arnd Bergmann <arnd@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Olof Johansson <olof@lixom.net>
Cc: SoC Team <soc@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL 0/5] SoC changes for 5.17
Date: Fri, 24 Dec 2021 09:11:39 -0800	[thread overview]
Message-ID: <7e480da8-0d54-2d62-0a8e-184901c974b6@gmail.com> (raw)
In-Reply-To: <CAK8P3a0RDZpLtWjMEU1QVWSjOoqRAH6QxQ+ZQnJc8LwaV7m+JQ@mail.gmail.com>

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!
-- 
Florian

       reply	other threads:[~2021-12-24 17:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAK8P3a0RDZpLtWjMEU1QVWSjOoqRAH6QxQ+ZQnJc8LwaV7m+JQ@mail.gmail.com>
2021-12-24 17:11 ` Florian Fainelli [this message]
2022-01-04 21:58   ` [GIT PULL 0/5] SoC changes for 5.17 Florian Fainelli
2022-01-05  0:40     ` Olof Johansson
     [not found]       ` <CAK8P3a3sBADt4Cu=LGbjHQpQ32O-BtFk1aQFwhL8Ar=M_gj6Xw@mail.gmail.com>
2022-01-10 18:32         ` Olof Johansson
2022-01-10 18:56           ` Florian Fainelli
2022-01-25 18:47           ` Bjorn Andersson

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=7e480da8-0d54-2d62-0a8e-184901c974b6@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=arnd@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=soc@kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).