From: patchwork-bot+linux-riscv@kernel.org
To: Conor Dooley <conor.dooley@microchip.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
conor@kernel.org, ajones@ventanamicro.com, Jason@zx2c4.com,
apatel@ventanamicro.com, heiko.stuebner@vrull.eu,
jszhang@kernel.org, linux-kernel@vger.kernel.org,
paul.walmsley@sifive.com
Subject: Re: [PATCH v1] RISC-V: convert new selectors of RISCV_ALTERNATIVE to dependencies
Date: Fri, 31 Mar 2023 00:50:17 +0000 [thread overview]
Message-ID: <168022381767.20027.13723928750136260683.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230324121240.3594777-1-conor.dooley@microchip.com>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Fri, 24 Mar 2023 12:12:41 +0000 you wrote:
> for-next contains two additional extensions that select
> RISCV_ALTERNATIVE. RISCV_ALTERNATIVE no longer needs to be selected by
> individual config options as it is now selected for !XIP_KERNEL builds
> by the top level RISCV option.
> These extensions rely on the alternative framework, so convert the
> "select"s to "depends on"s instead.
>
> [...]
Here is the summary with links:
- [v1] RISC-V: convert new selectors of RISCV_ALTERNATIVE to dependencies
https://git.kernel.org/riscv/c/d34a6b715a23
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:[~2023-03-31 0:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 12:12 [PATCH v1] RISC-V: convert new selectors of RISCV_ALTERNATIVE to dependencies Conor Dooley
2023-03-24 12:39 ` Andrew Jones
2023-03-31 0:43 ` Palmer Dabbelt
2023-03-31 0: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=168022381767.20027.13723928750136260683.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=Jason@zx2c4.com \
--cc=ajones@ventanamicro.com \
--cc=apatel@ventanamicro.com \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=heiko.stuebner@vrull.eu \
--cc=jszhang@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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