5 Firstly - make sure you've subscribed to the mailing list!
7 Next - when you contribute patches, you must abide by the Linux coding "Signed-off-by" concept. That is, that you did the work; that you don't know of any patent infringements introduced by your code; that you contribute you work under the same licence as the file falls under.
9 > Developer's Certificate of Origin 1.1
11 > By making a contribution to this project, I certify that:
13 > (a) The contribution was created in whole or in part by me and I
14 > have the right to submit it under the open source license
15 > indicated in the file; or
17 > (b) The contribution is based upon previous work that, to the best
18 > of my knowledge, is covered under an appropriate open source
19 > license and I have the right under that license to submit that
20 > work with modifications, whether created in whole or in part
21 > by me, under the same open source license (unless I am
22 > permitted to submit under a different license), as indicated
25 > (c) The contribution was provided directly to me by some other
26 > person who certified (a), (b) or (c) and I have not modified
29 > (d) I understand and agree that this project and the contribution
30 > are public and that a record of the contribution (including all
31 > personal information I submit with it, including my sign-off) is
32 > maintained indefinitely and may be redistributed consistent with
33 > this project or the open source license(s) involved.
35 So, whenever you send a patch or merge request, it must include a signed-off-by tag indicating you agree to the above.
37 That's it! Send a merge request or patch with a signed-off-by tag and be prepared to haggle with the maintainers / developers!