From: "Arnd Bergmann" <arnd@arndb.de>
To: "Adam Borowski" <kilobyte@angband.pl>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: "Winkler, Tomas" <tomas.winkler@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Usyskin, Alexander" <alexander.usyskin@intel.com>
Subject: Re: [PATCH] mei: make hdcp and pxp depend on X86 && PCI
Date: Tue, 25 Apr 2023 22:51:01 +0100 [thread overview]
Message-ID: <a8840c41-6245-4531-8b23-5c4e594c1ca9@app.fastmail.com> (raw)
In-Reply-To: <20230425152720.GA4155584@angband.pl>
On Tue, Apr 25, 2023, at 16:27, Adam Borowski wrote:
> On Tue, Apr 25, 2023 at 03:40:10PM +0200, Greg Kroah-Hartman wrote:
>> On Tue, Apr 25, 2023 at 01:52:10PM +0200, Adam Borowski wrote:
>> > On Tue, Apr 25, 2023 at 04:39:23AM +0000, Winkler, Tomas wrote:
>> > > What is the exact issue you are experiencing, can you add the error message this fixes?
>> >
>> > The problem doesn't trigger in mainline
>>
>> Then it's nothing we need to worry about in mainline. If/when other
>> changes ever happen to need it here in mainline, we will gladly take the
>> change.
>>
>> For obvious reasons, we can't take patches for issues outside of our
>> codebase. Nor do you want us to, as that way lies madness and an
>> unmaintainable mess.
>
> The problem in mainline is inconsistency: out of 6 config items, 4 repeat
> the "depends on X86 && PCI" line, the other 2 do not. There's indeed no
> immediate functional issue, but I'd argue that a dormant bug is still a bug.
>
> So we can fix the cosmetic (currently) issue on its own, or as part of the
> large patchset -- the latter having a side effect of stuffing your mailboxes
> more than needed (neither Greg, Arnd, nor Tomas are involved in other bits).
>
> But do the selects really require so much duplication? Perhaps I'm trying
> to fix the underlying issue wrong?
I think something along these lines would do (untested):
diff --git a/drivers/misc/mei/Kconfig b/drivers/misc/mei/Kconfig
index d21486d69df2..8e5d79cff80b 100644
--- a/drivers/misc/mei/Kconfig
+++ b/drivers/misc/mei/Kconfig
@@ -1,6 +1,6 @@
# SPDX-License-Identifier: GPL-2.0
# Copyright (c) 2003-2019, Intel Corporation. All rights reserved.
-config INTEL_MEI
+menuconfig INTEL_MEI
tristate "Intel Management Engine Interface"
depends on X86 && PCI
help
@@ -13,8 +13,6 @@ config INTEL_MEI
config INTEL_MEI_ME
tristate "ME Enabled Intel Chipsets"
- select INTEL_MEI
- depends on X86 && PCI
help
MEI support for ME Enabled Intel chipsets.
@@ -38,8 +36,6 @@ config INTEL_MEI_ME
config INTEL_MEI_TXE
tristate "Intel Trusted Execution Environment with ME Interface"
- select INTEL_MEI
- depends on X86 && PCI
help
MEI Support for Trusted Execution Environment device on Intel SoCs
@@ -48,9 +44,7 @@ config INTEL_MEI_TXE
config INTEL_MEI_GSC
tristate "Intel MEI GSC embedded device"
- depends on INTEL_MEI
depends on INTEL_MEI_ME
- depends on X86 && PCI
depends on DRM_I915
help
Intel auxiliary driver for GSC devices embedded in Intel graphics devices.
@@ -63,3 +57,4 @@ config INTEL_MEI_GSC
source "drivers/misc/mei/hdcp/Kconfig"
source "drivers/misc/mei/pxp/Kconfig"
+endmenu
next prev parent reply other threads:[~2023-04-25 21:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-23 13:51 kilobyte
2023-04-25 4:39 ` Winkler, Tomas
2023-04-25 11:52 ` Adam Borowski
2023-04-25 13:40 ` Greg Kroah-Hartman
2023-04-25 15:27 ` Adam Borowski
2023-04-25 15:43 ` [PATCH v2] mei: deduplicate X86 && PCI dependencies, make them apply to all subentries kilobyte
2023-04-25 16:16 ` Greg Kroah-Hartman
2023-04-25 21:51 ` Arnd Bergmann [this message]
2023-04-26 18:11 ` [PATCH] mei: make hdcp and pxp depend on X86 && PCI Winkler, Tomas
2023-04-28 5:50 ` Arnd Bergmann
2023-04-30 6:38 ` Winkler, Tomas
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=a8840c41-6245-4531-8b23-5c4e594c1ca9@app.fastmail.com \
--to=arnd@arndb.de \
--cc=alexander.usyskin@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kilobyte@angband.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=tomas.winkler@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®