From: Randy Dunlap <rdunlap@infradead.org>
To: Johannes Berg <johannes@sipsolutions.net>, linux-kernel@vger.kernel.org
Cc: Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Johannes Berg <johannes.berg@intel.com>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] drivers: char: SONYPI depends on HAS_IOPORT
Date: Tue, 17 Jun 2025 11:41:22 -0700 [thread overview]
Message-ID: <7f388a3f-6dcc-4989-9a4e-e15000069b68@infradead.org> (raw)
In-Reply-To: <20250606071255.7722-2-johannes@sipsolutions.net>
On 6/6/25 12:12 AM, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> It already depends on X86_32, but that's also set for ARCH=um.
> Recent changes made UML no longer have IO port access since
> it's not needed, but this driver uses it. Build it only for
> HAS_IOPORT. This is pretty much the same as depending on X86,
> but on the off-chance that HAS_IOPORT will ever be optional
> on x86 HAS_IOPORT is the real prerequisite.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202506060742.XR3HcxWA-lkp@intel.com/
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> drivers/char/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/char/Kconfig b/drivers/char/Kconfig
> index 8fb33c90482f..36295558dc85 100644
> --- a/drivers/char/Kconfig
> +++ b/drivers/char/Kconfig
> @@ -237,7 +237,7 @@ config APPLICOM
>
> config SONYPI
> tristate "Sony Vaio Programmable I/O Control Device support"
> - depends on X86_32 && PCI && INPUT
> + depends on X86_32 && PCI && INPUT && HAS_IOPORT
> depends on ACPI_EC || !ACPI
> help
> This driver enables access to the Sony Programmable I/O Control
--
~Randy
prev parent reply other threads:[~2025-06-17 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 7:12 Johannes Berg
2025-06-06 7:48 ` Arnd Bergmann
2025-06-17 18:41 ` Randy Dunlap [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=7f388a3f-6dcc-4989-9a4e-e15000069b68@infradead.org \
--to=rdunlap@infradead.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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
all inboxes | Powered by JetHome®