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:   Wed, 6 May 2020 14:46:20 +0200
From:   Linus Walleij <>
To:     Jonathan Bakker <>
Cc:     Jonathan Cameron <>,
        Hartmut Knaack <>,
        Lars-Peter Clausen <>,
        Peter Meerwald <>,
        Rob Herring <>,
        linux-iio <>,
        "" <>,
        Dmitry Torokhov <>,
        Kate Stewart <>,
        Greg KH <>,
        Thomas Gleixner <>,
        Linux Input <>
Subject: Re: [PATCH 2/5] input: misc: bma150: Conditionally disable bma023 support

On Sun, May 3, 2020 at 7:22 PM Jonathan Bakker <> wrote:

> The bma180 IIO driver has been extended for support for bma023.
> However, this could cause conflicts with this driver.  Since some
> setups may depend upon the evdev setup, disable support in this
> driver for the bma023 only when the IIO driver is being built.
> Signed-off-by: Jonathan Bakker <>

I would just fix this with KConfig instead, like add mutually
exclusive depends on these two drivers.

Set this input driver as:
depends on BMA180=n

And the IIO driver as:
depends on INPUT_BMA150=n

It's a rough measure but this input driver should anyway
go away.

Linus Walleij

Powered by blists - more mailing lists