bdev: fix NULL pointer dereference
[linux-2.6-block.git] / firmware / README.AddingFirmware
CommitLineData
0f8e5c29
DW
1
2 DO NOT ADD FIRMWARE TO THIS DIRECTORY.
3 ======================================
4
5This directory is only here to contain firmware images extracted from old
6device drivers which predate the common use of request_firmware().
7
8As we update those drivers to use request_firmware() and keep a clean
9separation between code and firmware, we put the extracted firmware
10here.
11
12This directory is _NOT_ for adding arbitrary new firmware images. The
13place to add those is the separate linux-firmware repository:
14
7b21a202 15 git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
0f8e5c29
DW
16
17That repository contains all these firmware images which have been
18extracted from older drivers, as well various new firmware images which
19we were never permitted to include in a GPL'd work, but which we _have_
20been permitted to redistribute under separate cover.
21
22To submit firmware to that repository, please send either a git binary
23diff or preferably a git pull request to:
de88d8be
BH
24 linux-firmware@kernel.org
25and also cc: to related mailing lists.
0f8e5c29
DW
26
27Your commit should include an update to the WHENCE file clearly
28identifying the licence under which the firmware is available, and
29that it is redistributable. If the licence is long and involved, it's
30permitted to include it in a separate file and refer to it from the
31WHENCE file.
de88d8be 32And if it were possible, a changelog of the firmware itself.
0f8e5c29
DW
33
34Ideally, your commit should contain a Signed-Off-By: from someone
35authoritative on the licensing of the firmware in question (i.e. from
36within the company that owns the code).
de88d8be
BH
37
38
39WARNING:
40=======
41
42Don't send any "CONFIDENTIALITY STATEMENT" in your e-mail, patch or
43request. Otherwise your firmware _will never be accepted_.
44
45Maintainers are really busy, so don't expect a prompt reply.