From: patchwork-bot+linux-riscv@kernel.org
To: Conor Dooley <conor@kernel.org>
Cc: linux-riscv@lists.infradead.org, conor.dooley@microchip.com,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, prabhakar.mahadev-lad.rj@bp.renesas.com,
geert+renesas@glider.be, linux-renesas-soc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] RISC-V: run savedefconfig for defconfig
Date: Tue, 23 Jul 2024 12:58:36 +0000 [thread overview]
Message-ID: <172173951658.10883.5835597869579224496.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240717-shrubs-concise-51600886babf@spud>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 17 Jul 2024 14:29:24 +0100 you wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> It's been a while since this was run, and there's a few things that have
> changed. Firstly, almost all of the Renesas stuff vanishes because the
> config for the RZ/Five is gated behind NONPORTABLE. Several options
> (like CONFIG_PM) are removed as they are the default values.
>
> [...]
Here is the summary with links:
- [v1] RISC-V: run savedefconfig for defconfig
https://git.kernel.org/riscv/c/82b461680651
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
prev parent reply other threads:[~2024-07-23 12:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 13:29 [PATCH v1] RISC-V: run savedefconfig for defconfig Conor Dooley
2024-07-19 11:05 ` Geert Uytterhoeven
2024-07-22 11:21 ` Conor Dooley
2024-07-23 12:58 ` 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=172173951658.10883.5835597869579224496.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
/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