public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Paul Walmsley <pjw@kernel.org>
Cc: linux-riscv@lists.infradead.org, torvalds@linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] RISC-V updates for v7.1
Date: Thu, 30 Apr 2026 04:08:36 +0000	[thread overview]
Message-ID: <177752211655.2274119.2873579149327343188.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ecdaf68d-1fe5-0b55-ff6a-a2710c05ccef@kernel.org>

Hello:

This pull request was applied to riscv/linux.git (for-next)
by Linus Torvalds <torvalds@linux-foundation.org>:

On Thu, 23 Apr 2026 18:07:29 -0600 (MDT) you wrote:
> Linus,
> 
> Please pull these RISC-V updates for v7.1.  I'm sending this pull
> request much later than I or you would like to see it.  I do not plan
> for this to be a regular occurrence.  My goal is to send RISC-V PRs
> much earlier in the merge window (if not before it opens).
> 
> [...]

Here is the summary with links:
  - [GIT,PULL] RISC-V updates for v7.1
    https://git.kernel.org/riscv/c/feff82eb5f40

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



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

      parent reply	other threads:[~2026-04-30  4:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-24  0:07 [GIT PULL] RISC-V updates for v7.1 Paul Walmsley
2026-04-24  0:32 ` Nathan Chancellor
2026-04-24 13:26   ` Paul Walmsley
2026-04-24 18:32 ` pr-tracker-bot
2026-04-30  3:25 ` patchwork-bot+linux-riscv
2026-04-30  4:08 ` patchwork-bot+linux-riscv [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=177752211655.2274119.2873579149327343188.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=pjw@kernel.org \
    --cc=torvalds@linux-foundation.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