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: <20190111095924.GA555@kroah.com>
Date:   Fri, 11 Jan 2019 10:59:24 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc:     Luis Chamberlain <mcgrof@...nel.org>, linux-kbuild@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        Michal Marek <michal.lkml@...kovi.net>,
        "Rafael J. Wysocki" <rafael@...nel.org>
Subject: Re: [PATCH] firmware_loader: move firmware/ to
 drivers/base/firmware_loader/builtin/

On Fri, Jan 11, 2019 at 06:52:00PM +0900, Masahiro Yamada wrote:
> Currently, the 'firmware' directory only contains a single Makefile
> to embed extra firmware into the kernel.
> 
> Move it to the more relevant place.

So this moves any "build in" firmware to need to be placed in
drivers/base/firmare_loader/builtin/ instead of firmware/builtin/ ?  If
so, why?  That seems like a lot of extra work for people now.  And
burrying it down in the drivers/base/ directory is not obvious at all.

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ