Documentation: clarify firmware_class provenance and why we can't rename the module
authorLuis R. Rodriguez <mcgrof@kernel.org>
Thu, 10 May 2018 20:08:50 +0000 (13:08 -0700)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Mon, 14 May 2018 14:46:10 +0000 (16:46 +0200)
commitf0a462970ee19930518b03798a21cfdb3fd35877
tree52074a043eb0a62e1cddbc4b28734c7c81c5da5f
parent0b92d3f6802609e5c5ec30571296c68cfb2cd4aa
Documentation: clarify firmware_class provenance and why we can't rename the module

Clarify the provenance of the firmware loader firmware_class module name
and why we cannot rename the module in the future.

Reviewed-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Reviewed-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Luis R. Rodriguez <mcgrof@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Documentation/driver-api/firmware/fallback-mechanisms.rst