public inbox for soc@kernel.org
 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/3] Broadcom devicetree changes for 6.5
Date: Thu, 22 Jun 2023 16:10:30 +0000	[thread overview]
Message-ID: <168745023002.12309.1432980204429131078.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230619134920.3384844-1-florian.fainelli@broadcom.com>

Hello:

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

On Mon, 19 Jun 2023 06:49:18 -0700 you wrote:
> The following changes since commit ac9a78681b921877518763ba0e89202254349d1b:
> 
>   Linux 6.4-rc1 (2023-05-07 13:34:35 -0700)
> 
> are available in the Git repository at:
> 
>   https://github.com/Broadcom/stblinux.git tags/arm-soc/for-6.5/devicetree
> 
> [...]

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

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



      parent reply	other threads:[~2023-06-22 16:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-19 13:49 [GIT PULL 1/3] Broadcom devicetree changes for 6.5 Florian Fainelli
2023-06-19 13:49 ` [GIT PULL 2/3] Broadcom devicetree-arm64 " Florian Fainelli
2023-06-19 13:49 ` [GIT PULL 3/3] Broadcom maintainers " Florian Fainelli
2023-06-22 15:29   ` Arnd Bergmann
2023-06-20 21:21 ` [GIT PULL 1/3] Broadcom devicetree " patchwork-bot+linux-soc
2023-06-22 16:10 ` 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=168745023002.12309.1432980204429131078.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