linux-kernel - Re: [PATCH 2/2] mei: Add MEI hardware support for IVSC device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ZWcR5EUADPkGSXng@kekkonen.localdomain>
Date:   Wed, 29 Nov 2023 10:26:44 +0000
From:   Sakari Ailus <sakari.ailus@...ux.intel.com>
To:     Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc:     Wentong Wu <wentong.wu@...el.com>, gregkh@...uxfoundation.org,
        tomas.winkler@...el.com, hdegoede@...hat.com,
        alexander.usyskin@...el.com, zhifeng.wang@...el.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] mei: Add MEI hardware support for IVSC device

On Wed, Nov 29, 2023 at 12:21:32PM +0200, Andy Shevchenko wrote:
> On Wed, Nov 29, 2023 at 09:26:47AM +0000, Sakari Ailus wrote:
> > On Tue, Nov 28, 2023 at 08:34:06PM +0800, Wentong Wu wrote:
> 
> ...
> 
> > I wouldn't mind having a single Kconfig option for the two drivers either.
> > They're always used together, aren't they?
> 
> As far as I understand the topology, here we have one "core" driver and
> one "leaf" driver. So, in my understanding they may not go together as
> it will bring unneeded code in the future in some configurations.

Yes, that is possible in the future if other clients appear. But will there
be any? Both drivers appear to be related to IVSC.

-- 
Sakari Ailus