From: "Arnd Bergmann" <arnd@arndb.de>
To: "Geert Uytterhoeven" <geert@linux-m68k.org>,
"Simon Richter" <Simon.Richter@hogyros.de>
Cc: "Alexander Usyskin" <alexander.usyskin@intel.com>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
Date: Thu, 29 Jan 2026 09:53:32 +0100 [thread overview]
Message-ID: <1d985068-47a7-4a25-b387-e69a74873a61@app.fastmail.com> (raw)
In-Reply-To: <CAMuHMdVEdps0_H-Yr0aO+MDxZjXWjoCAY-bZyr04HYVdYQCwSw@mail.gmail.com>
On Thu, Jan 29, 2026, at 09:17, Geert Uytterhoeven wrote:
> On Thu, 29 Jan 2026 at 05:45, Simon Richter <Simon.Richter@hogyros.de> wrote:
>>
>> DRM_I915 depends on PCI && X86 (so "X86 || DRM_I915" is redundant, which
>> is why I didn't add it in my version of the patch. If DRM_I915 is useful
>> on non-x86 we might want to change that as well.
>
> Then the dependency of DRM_I915 on X86 should be dropped first...
This is not easily done, with the amount of 'select' statements
from the I915 drive, including X86_PLATFORM_DEVICES and ACPI_WMI.
At the minimum, changing this should involve turning a lot of
these into 'depends on' to avoid dependency loops, plus
build testing random configurations.
Arnd
next prev parent reply other threads:[~2026-01-29 8:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 19:11 Geert Uytterhoeven
2026-01-28 6:41 ` Usyskin, Alexander
2026-01-28 6:50 ` Arnd Bergmann
2026-01-28 6:57 ` Usyskin, Alexander
2026-01-28 7:24 ` Arnd Bergmann
2026-01-29 4:45 ` Simon Richter
2026-01-29 5:53 ` Usyskin, Alexander
2026-01-30 21:15 ` Rodrigo Vivi
2026-02-01 10:15 ` Usyskin, Alexander
2026-02-02 9:33 ` Geert Uytterhoeven
2026-02-02 11:43 ` Usyskin, Alexander
2026-01-29 8:17 ` Geert Uytterhoeven
2026-01-29 8:53 ` Arnd Bergmann [this message]
2026-01-29 9:01 ` Usyskin, Alexander
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=1d985068-47a7-4a25-b387-e69a74873a61@app.fastmail.com \
--to=arnd@arndb.de \
--cc=Simon.Richter@hogyros.de \
--cc=alexander.usyskin@intel.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®