From: Jeremy Kerr <jk@ozlabs.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] serial: 8250: SERIAL_8250_ASPEED_VUART should depend on ARCH_ASPEED
Date: Mon, 11 Jul 2022 18:40:38 +0800 [thread overview]
Message-ID: <74b98265ff9638ad7a06a58ef0dea1758396744f.camel@ozlabs.org> (raw)
In-Reply-To: <259138c372d433005b4871789ef9ee8d15320307.1657528861.git.geert+renesas@glider.be>
Hi Geert,
> The Aspeed Virtual UART is only present on Aspeed BMC platforms.
> Hence add a dependency on ARCH_ASPEED, to prevent asking the user
> about this driver when configuring a kernel without Aspeed BMC
> support.
All fine by me. It'd be super weird if this hardware appeared on a
non-ASPEED platform.
Reviewed-by: Jeremy Kerr <jk@ozlabs.org>
Cheers,
Jeremy
prev parent reply other threads:[~2022-07-11 11:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 8:42 [PATCH] serial: 8250: SERIAL_8250_ASPEED_VUART should depend on ARCH_ASPEED Geert Uytterhoeven
2022-07-11 10:40 ` Jeremy Kerr [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=74b98265ff9638ad7a06a58ef0dea1758396744f.camel@ozlabs.org \
--to=jk@ozlabs.org \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.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 NNTP newsgroup(s).