All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-soc@kernel.org
To: Thierry Reding <thierry.reding@kernel.org>
Cc: soc@kernel.org
Subject: Re: [GIT PULL 1/4] dt-bindings: Changes for v7.3-rc1
Date: Sun, 09 Aug 2026 02:10:05 +0000	[thread overview]
Message-ID: <178624140589.2813131.27669212901936824.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260802165148.1259649-1-thierry.reding@kernel.org>

Hello:

This pull request was applied to soc/soc.git (for-next)
by Alexandre Belloni <alexandre.belloni@bootlin.com>:

On Sun,  2 Aug 2026 18:51:44 +0200 you wrote:
> From: Thierry Reding <thierry.reding@gmail.com>
> 
> Hi ARM SoC maintainers,
> 
> The following changes since commit dc59e4fea9d83f03bad6bddf3fa2e52491777482:
> 
>   Linux 7.2-rc1 (2026-06-28 12:01:31 -0700)
> 
> [...]

Here is the summary with links:
  - [GIT,PULL,1/4] dt-bindings: Changes for v7.3-rc1
    https://git.kernel.org/soc/soc/c/36a05549410a
  - [GIT,PULL,2/4] ARM: Core Tegra changes for v7.3-rc1
    (no matching commit)
  - [GIT,PULL,3/4] soc/tegra: Changes for v7.3-rc1
    (no matching commit)
  - [GIT,PULL,4/4] arm64: tegra: Device tree changes for v7.3-rc1
    https://git.kernel.org/soc/soc/c/b981359d9eca

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



      parent reply	other threads:[~2026-08-09  2:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-02 16:51 [GIT PULL 1/4] dt-bindings: Changes for v7.3-rc1 Thierry Reding
2026-08-02 16:51 ` [GIT PULL 2/4] ARM: Core Tegra changes " Thierry Reding
2026-08-02 16:51 ` [GIT PULL 3/4] soc/tegra: Changes " Thierry Reding
2026-08-02 16:51 ` [GIT PULL 4/4] arm64: tegra: Device tree changes " Thierry Reding
2026-08-04 20:20 ` [GIT PULL 1/4] dt-bindings: Changes " patchwork-bot+linux-soc
2026-08-09  2: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=178624140589.2813131.27669212901936824.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-soc@kernel.org \
    --cc=soc@kernel.org \
    --cc=thierry.reding@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.