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: <CAHk-=wgF_0+au4cz-ZmH4qOpgDWmmbJC101fh_RVAbsJRH7d-Q@mail.gmail.com>
Date:   Sat, 8 Oct 2022 16:23:41 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Hans de Goede <hdegoede@...hat.com>
Cc:     Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        Lee Jones <lee@...nel.org>, Mark Brown <broonie@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] Backlight for v6.1

On Sat, Oct 8, 2022 at 12:59 PM Hans de Goede <hdegoede@...hat.com> wrote:
> >
> > Yeah, I don't expect he driver to work on real hardware,
>
> I'm not sure what you mean here. I guess you mean that you
> do not expect to be able to test the driver on real hw
> yourself?

Well, that too, but I really along the lines of "make it build as a
module when I2C_DESIGNWARE_PLATFORM is a module"

Because if it depends on some symbols from I2C_DESIGNWARE_PLATFORM,
and that one can be a module, then the Intel PMI driver also needs to
be built as a module to just get the build coverage, at least.

And I can imagine that that will not work very well on actual hardware
with some of these core drivers that may want to initialize early?

But I'd love to at least have the build coverage.

                 Linus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ