1/10/2023 0 Comments Radioshark linux![]() 79 80 Descriptions of section entries and preferred 81 - 82 83 M: *Mail* patches to: FullName 148 L: 149 S: Odd Fixes 150 F: Documentation/networking/device_driver 151 F: drivers/net/ethernet/3com/3c59x.c 152 153 3CR990 NETWORK DRIVER 154 M: David Dillow 155 L: 156 S: Maintained 157 F: drivers/net/ethernet/3com/typhoon* 158 159 3WARE SAS/SATA-RAID SCSI DRIVERS (3W-XXXX, 3W- 160 M: Adam Radford 161 L: 162 S: Supported 163 W: 164 F: drivers/scsi/3w-* 165 166 53C700 AND 53C700-66 SCSI DRIVER 167 M: "James E.J. 75 better and faster in the usual public 76 Documentation/admin-guide/security-bug 77 78 8. For example, 72 not represent an immediate threat and 73 and ideally, should come with a patch 74 automated reports to this list either. Please only Cc: this li 70 that the bug would present a short-ter 71 were publicly disclosed. ![]() Please keep in mind 68 a small set of people who can be effic 69 verified bugs. When sending security related changes 66 please Cc: especi 67 does not respond. Make sure you have the right to send a 62 do changes at work you may find your e 63 not you. The cu 58 "Developer's Certificate of Origin" (D 59 Documentation/process/submitting-patch 60 61 6. If it does 53 or does something very odd once a mont 54 55 PLEASE remember that submissions must 56 of the Linux Foundation certificate of 57 include a Signed-off-by: line. It avoids people being missed o 50 it easier to know who wants adding and 51 52 PLEASE document known bugs. Sometimes this means 35 your driver to get around a problem ac 36 generalized kernel feature ready for n 37 38 PLEASE check your patch with the autom 39 (scripts/) to catch trivi 40 See Documentation/process/coding-style 41 42 PLEASE CC: the maintainers and mailing 43 by ``scripts/get_.`` The 44 script will be best if you have git in 45 your changes in a branch derived from 46 See Documentation/process/submitting-p 47 48 PLEASE try to include any credit lines 49 patch. These aren't as s 33 job the maintainers (and especially Li 34 looking the same. Make a patch available to the relevant 30 ``diff -u`` to make the patch easy to 31 changes sent back with seemingly silly 32 and variable names. ![]() When you are happy with a change make 27 testing and await feedback. In particular check th 24 module and built into the kernel. Make sure your changes compile correct 23 configurations. Try to release a few ALPHA test versio 15 them onto the kernel channel and await 16 important for device drivers, because 17 you will find things like the fact ver 18 a magic fix you didn't know about, or 19 chips on a board and not its name. Always *test* your changes, however sm 12 5 people, preferably many more. 7 8 Tips for patch submitters 9 - 10 11 1. Not all of these g 6 trivial patch so apply some common sense. ~ ~ ~ ~ ~ ~ ~ ~ĭiff markup Differences between /MAINTAINERS (Version linux-6.0) and /MAINTAINERS (Version linux-3.5.7)ġ List of maintainers and how to submit kernel c 2 = 3 4 Please try to follow the guidelines below.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |