public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Yixun Lan <dlan@gentoo.org>
Cc: linux-riscv@lists.infradead.org, conor@kernel.org,
	paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, alex@ghiti.fr, guodong@riscstar.com,
	linux-kernel@vger.kernel.org, spacemit@lists.linux.dev
Subject: Re: [PATCH] riscv: defconfig: run savedefconfig to reorder it
Date: Thu, 12 Jun 2025 21:40:28 +0000	[thread overview]
Message-ID: <174976442875.118664.14858626447477465303.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250611-01-riscv-defconfig-v1-1-b48fc3517498@gentoo.org>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@dabbelt.com>:

On Wed, 11 Jun 2025 22:56:04 +0800 you wrote:
> Changes to defconfig should be always updated via 'make
> savedefconfig', run this command to make it aligned again.
> 
> This will ease the effort of reviewing changes of defconfig
> in the future.
> 
> Signed-off-by: Yixun Lan <dlan@gentoo.org>
> 
> [...]

Here is the summary with links:
  - riscv: defconfig: run savedefconfig to reorder it
    https://git.kernel.org/riscv/c/d958097bdf88

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



  parent reply	other threads:[~2025-06-12 21:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-11 14:56 [PATCH] riscv: defconfig: run savedefconfig to reorder it Yixun Lan
2025-06-12  8:37 ` Alexandre Ghiti
2025-06-12  9:32   ` Yixun Lan
2025-06-12 13:12     ` Alexandre Ghiti
2025-06-12 18:57       ` Palmer Dabbelt
2025-06-19  3:32         ` Guodong Xu
2025-06-12 21:40 ` patchwork-bot+linux-riscv [this message]
2025-09-14 15:44   ` Conor Dooley

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=174976442875.118664.14858626447477465303.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor@kernel.org \
    --cc=dlan@gentoo.org \
    --cc=guodong@riscstar.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=spacemit@lists.linux.dev \
    /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