public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Samuel Holland <samuel.holland@sifive.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, raven@themaw.net,
	paul.walmsley@sifive.com, svenjoac@gmx.de,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: Remove obsolete rv32_defconfig file
Date: Fri, 05 Jan 2024 21:50:27 +0000	[thread overview]
Message-ID: <170449142768.26226.3943147801325806226.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231121225320.3430550-1-samuel.holland@sifive.com>

Hello:

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

On Tue, 21 Nov 2023 14:53:18 -0800 you wrote:
> This file is not used since commit 72f045d19f25 ("riscv: Fixup
> difference with defconfig"), where it was replaced by the
> 32-bit.config fragment. Delete the old file to avoid any confusion.
> 
> Signed-off-by: Samuel Holland <samuel.holland@sifive.com>
> ---
> 
> [...]

Here is the summary with links:
  - riscv: Remove obsolete rv32_defconfig file
    https://git.kernel.org/riscv/c/f4727fe60ff6

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:[~2024-01-05 21:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-21 22:53 [PATCH] riscv: Remove obsolete rv32_defconfig file Samuel Holland
2023-11-22  0:08 ` Conor Dooley
2024-01-05 21:50 ` 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=170449142768.26226.3943147801325806226.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=raven@themaw.net \
    --cc=samuel.holland@sifive.com \
    --cc=svenjoac@gmx.de \
    /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