From: Randy Dunlap <rdunlap@infradead.org>
To: Masahiro Yamada <masahiroy@kernel.org>, linux-kbuild@vger.kernel.org
Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
Matt Turner <mattst88@gmail.com>,
Richard Henderson <richard.henderson@linaro.org>,
linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] alpha: merge two entries for CONFIG_ALPHA_GAMMA
Date: Thu, 15 Feb 2024 15:27:57 -0800 [thread overview]
Message-ID: <b3f86324-afa2-49b7-9565-28f41aaf3334@infradead.org> (raw)
In-Reply-To: <20240215141120.1911369-2-masahiroy@kernel.org>
Hi,
On 2/15/24 06:11, Masahiro Yamada wrote:
> There are two entries for CONFIG_ALPHA_GAMMA, with the second one
> 7 lines below. Merge them together.
>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> ---
>
> arch/alpha/Kconfig | 10 +++-------
> 1 file changed, 3 insertions(+), 7 deletions(-)
>
> diff --git a/arch/alpha/Kconfig b/arch/alpha/Kconfig
> index 70e8343d00ba..581ca8c73d67 100644
> --- a/arch/alpha/Kconfig
> +++ b/arch/alpha/Kconfig
> @@ -390,16 +390,12 @@ config ALPHA_PRIMO
> Say Y if you have an AS 1000 5/xxx or an AS 1000A 5/xxx.
>
> config ALPHA_GAMMA
> - bool "EV5 CPU(s) (model 5/xxx)?"
> - depends on ALPHA_SABLE
> + bool "EV5 CPU(s) (model 5/xxx)?" if ALPHA_SABLE
> + depends on ALPHA_SABLE || ALPHA_GAMMA
depends on ALPHA_SABLE || ALPHA_LYNX
??
> + default ALPHA_LYNX
> help
> Say Y if you have an AS 2000 5/xxx or an AS 2100 5/xxx.
>
> -config ALPHA_GAMMA
> - bool
> - depends on ALPHA_LYNX
> - default y
> -
> config ALPHA_T2
> bool
> depends on ALPHA_SABLE || ALPHA_LYNX
--
#Randy
next prev parent reply other threads:[~2024-02-15 23:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 14:11 [PATCH 1/2] alpha: merge two entries for CONFIG_ALPHA_EV4 Masahiro Yamada
2024-02-15 14:11 ` [PATCH 2/2] alpha: merge two entries for CONFIG_ALPHA_GAMMA Masahiro Yamada
2024-02-15 23:27 ` Randy Dunlap [this message]
2024-02-16 2:13 ` Masahiro Yamada
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=b3f86324-afa2-49b7-9565-28f41aaf3334@infradead.org \
--to=rdunlap@infradead.org \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mattst88@gmail.com \
--cc=richard.henderson@linaro.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).