Linux SOC development
 help / color / mirror / Atom feed
From: patchwork-bot+linux-soc@kernel.org
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: soc@kernel.org
Subject: Re: [PATCH v2 0/2] arm64: Kconfig.platforms: Group vendors together
Date: Fri, 02 Sep 2022 11:00:24 +0000	[thread overview]
Message-ID: <166211642428.12856.14895962445441065204.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220829173830.3567047-1-f.fainelli@gmail.com>

Hello:

This series was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:

On Mon, 29 Aug 2022 10:38:27 -0700 you wrote:
> This is a follow up from:
> https://lore.kernel.org/all/20220712164235.40293-1-f.fainelli@gmail.com/
> 
> such that we have SoCs from the same vendor grouped into a menuconfig to
> be visually nicer and assist in selecting the specific SoCs.
> 
> Florian Fainelli (2):
>   arm64: Kconfig.platforms: Re-organized Broadcom menu
>   arm64: Kconfig.platforms: Group NXP platforms together
> 
> [...]

Here is the summary with links:
  - [v2,1/2] arm64: Kconfig.platforms: Re-organized Broadcom menu
    https://git.kernel.org/soc/soc/c/96796c914b84
  - [v2,2/2] arm64: Kconfig.platforms: Group NXP platforms together
    https://git.kernel.org/soc/soc/c/566e373fe047

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-09-02 11:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29 17:38 [PATCH v2 0/2] arm64: Kconfig.platforms: Group vendors together Florian Fainelli
2022-08-29 17:38 ` [PATCH v2 1/2] arm64: Kconfig.platforms: Re-organized Broadcom menu Florian Fainelli
2022-08-29 17:38 ` [PATCH v2 2/2] arm64: Kconfig.platforms: Group NXP platforms together Florian Fainelli
2022-09-15 16:08   ` Olof Johansson
2022-09-15 20:52     ` Florian Fainelli
2022-09-15 23:57       ` Olof Johansson
2022-09-02 11:00 ` patchwork-bot+linux-soc [this message]

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=166211642428.12856.14895962445441065204.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-soc@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=soc@kernel.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