Linux SOC development
 help / color / mirror / Atom feed
From: patchwork-bot+linux-soc@kernel.org
To: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: soc@kernel.org
Subject: Re: [GIT PULL 1/4] Broadcom devicetree changes for 6.12
Date: Fri, 11 Oct 2024 10:59:07 +0000	[thread overview]
Message-ID: <172864434726.2676212.13828028487176910757.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240906180643.2275460-1-florian.fainelli@broadcom.com>

Hello:

This pull request was applied to soc/soc.git (arm/fixes)
by Arnd Bergmann <arnd@arndb.de>:

On Fri,  6 Sep 2024 11:06:40 -0700 you wrote:
> The following changes since commit 8400291e289ee6b2bf9779ff1c83a291501f017b:
> 
>   Linux 6.11-rc1 (2024-07-28 14:19:55 -0700)
> 
> are available in the Git repository at:
> 
>   https://github.com/Broadcom/stblinux.git tags/arm-soc/for-6.12/devicetree
> 
> [...]

Here is the summary with links:
  - [GIT,PULL,1/4] Broadcom devicetree changes for 6.12
    https://git.kernel.org/soc/soc/c/ceb7d8adf640
  - [GIT,PULL,2/4] Broadcom devicetree-arm64 changes for 6.12
    (no matching commit)
  - [GIT,PULL,3/4] Broadcom drivers changes for 6.12
    (no matching commit)
  - [GIT,PULL,4/4] Broadcom soc changes for 6.12
    (no matching commit)

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



      parent reply	other threads:[~2024-10-11 10:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-06 18:06 [GIT PULL 1/4] Broadcom devicetree changes for 6.12 Florian Fainelli
2024-09-06 18:06 ` [GIT PULL 2/4] Broadcom devicetree-arm64 " Florian Fainelli
2024-09-06 18:06 ` [GIT PULL 3/4] Broadcom drivers " Florian Fainelli
2024-09-06 18:06 ` [GIT PULL 4/4] Broadcom soc " Florian Fainelli
2024-09-11  9:20 ` [GIT PULL 1/4] Broadcom devicetree " patchwork-bot+linux-soc
2024-10-11 10:59 ` 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=172864434726.2676212.13828028487176910757.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-soc@kernel.org \
    --cc=florian.fainelli@broadcom.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