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  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]
Date:   Mon, 18 May 2020 20:37:03 -0700
From:   Bjorn Andersson <>
To:     Viresh Kumar <>
Cc:     Greg Kroah-Hartman <>,
        Georgi Djakov <>,
        Vincent Guittot <>,
        Linux PM list <>,
        lkml <>,
        Arnd Bergmann <>,
        Matthias Kaehlcke <>
Subject: Re: [PATCH] interconnect: Disallow interconnect core to be built as
 a module

On Mon 18 May 20:31 PDT 2020, Viresh Kumar wrote:

> On 18-05-20, 11:40, Bjorn Andersson wrote:
> > It most certainly does.
> > 
> > With INTERCONNECT as a bool we can handle its absence with stub
> > functions - like every other framework does. But as a tristate then
> > every driver with a call to the interconnect api needs an entry in
> > Kconfig to ensure the client driver must be a module if the interconnect
> > framework is.
> This patch has been pushed to linux-next a few days back.

Thanks Viresh, I had missed that.


Powered by blists - more mailing lists