Linux SOC development
 help / color / mirror / Atom feed
From: patchwork-bot+linux-soc@kernel.org
To: Sudeep Holla <sudeep.holla@kernel.org>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] ARM: vexpress: Fixes for v7.4
Date: Tue, 13 Oct 2026 16:10:39 +0000	[thread overview]
Message-ID: <179190783926.417156.8943700807347309285.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261007150034.624664-1-sudeep.holla@kernel.org>

Hello:

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

On Wed,  7 Oct 2026 16:00:31 +0100 you wrote:
> Hi ARM SoC Team,
> 
> Please pull ! These came in recently and are in -next for a week now.
> I am sending these early for v7.4 as fixes instead of waiting until -rc1.
> 
> Regards,
> Sudeep
> 
> [...]

Here is the summary with links:
  - [GIT,PULL] ARM: vexpress: Fixes for v7.4
    https://git.kernel.org/soc/soc/c/19e5b00239f1

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



      reply	other threads:[~2026-10-13 16:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07 15:00 [GIT PULL] ARM: vexpress: Fixes for v7.4 Sudeep Holla
2026-10-13 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=179190783926.417156.8943700807347309285.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-soc@kernel.org \
    --cc=soc@kernel.org \
    --cc=sudeep.holla@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