From: patchwork-bot+linux-soc@kernel.org
To: Drew Fustini <fustini@kernel.org>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] RISC-V defconfig changes for v7.3
Date: Fri, 24 Jul 2026 16:40:17 +0000 [thread overview]
Message-ID: <178491121788.3229915.9040423834090729571.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <al+cTw/+z7xoJXxp@x1>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Tue, 21 Jul 2026 09:20:31 -0700 you wrote:
> Hi, I created my riscv-confg branches to shepard defconfig patches
> related to the riscv platforms that I maintain. The branches are in
> linux-next. For 7.3, there is just a single patch for the WiFi driver on
> the TH1520-based LPi4a.
>
> Thanks,
> Drew
>
> [...]
Here is the summary with links:
- [GIT,PULL] RISC-V defconfig changes for v7.3
https://git.kernel.org/soc/soc/c/6495ae297ceb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-07-24 16:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 16:20 [GIT PULL] RISC-V defconfig changes for v7.3 Drew Fustini
2026-07-24 16:40 ` 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=178491121788.3229915.9040423834090729571.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=fustini@kernel.org \
--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