linux-dev/drivers/base/firmware_loader/builtin/main.c, branch linus/masterLinux kernel development work - see feature brancheshttps://git.zx2c4.com/linux-dev/atom/drivers/base/firmware_loader/builtin/main.c?h=linus%2Fmaster2021-10-22T12:13:53Zfirmware_loader: move struct builtin_fw to the only place used2021-10-22T12:13:53ZLuis Chamberlainmcgrof@kernel.org2021-10-21T15:58:37Zurn:sha1:e2e2c0f20f321b0ec36e8bde467259c0adf1fecb
Now that x86 doesn't abuse picking at internals to the firmware
loader move out the built-in firmware struct to its only user.
Reviewed-by: Borislav Petkov <bp@suse.de>
Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
Link: https://lore.kernel.org/r/20211021155843.1969401-5-mcgrof@kernel.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
firmware_loader: formalize built-in firmware API2021-10-22T12:13:44ZLuis Chamberlainmcgrof@kernel.org2021-10-21T15:58:34Zurn:sha1:48d09e97876bed4bcc503d528bdba8c907e43cb3
Formalize the built-in firmware with a proper API. This can later
be used by other callers where all they need is built-in firmware.
We export the firmware_request_builtin() call for now only
under the TEST_FIRMWARE symbol namespace as there are no
direct modular users for it. If they pop up they are free
to export it generally. Built-in code always gets access to
the callers and we'll demonstrate a hidden user which has been
lurking in the kernel for a while and the reason why using a
proper API was better long term.
Reviewed-by: Borislav Petkov <bp@suse.de>
Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
Link: https://lore.kernel.org/r/20211021155843.1969401-2-mcgrof@kernel.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>