User Tools

Site Tools


en:developers:documentation:submittingpatches

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:developers:documentation:submittingpatches [2018/04/13 13:24]
Kalle Valo Add section for top posting
en:developers:documentation:submittingpatches [2018/06/14 08:10] (current)
Kalle Valo [More patch work references] Change title, "patch work" is easy to confuse with patchwork (the tool)
Line 336: Line 336:
 More info: http://​www.idallen.com/​topposting.html More info: http://​www.idallen.com/​topposting.html
  
 +==== Use RFC or RFT for patches not ready ====
  
-===== More patch work references =====+If the patches are not yet ready to be applied by the maintainer mark them as RFC (Request For Comments) or RFC (Request For Test), this way the maintainer can easily see that the patch should not be applied yet. This saves a lot of maintainer'​s time. 
 + 
 + 
 +===== More references =====
  
 Here is a list of links to help you write better patches ​ Here is a list of links to help you write better patches ​
Line 345: Line 349:
   * [[http://​linux.yyz.us/​patch-format.html|http://​linux.yyz.us/​patch-format.html]] ​   * [[http://​linux.yyz.us/​patch-format.html|http://​linux.yyz.us/​patch-format.html]] ​
   * [[https://​www.ozlabs.org/​~akpm/​stuff/​tpp.txt|Andrew Morton'​s ''​The perfect patch''​]] ​   * [[https://​www.ozlabs.org/​~akpm/​stuff/​tpp.txt|Andrew Morton'​s ''​The perfect patch''​]] ​
 +  * [[http://​lkml.kernel.org/​r/​20171026223701.GA25649@bhelgaas-glaptop.roam.corp.google.com|Make Bjorn'​s life easier (and grease the path of your patch)]]
en/developers/documentation/submittingpatches.1523625882.txt.gz · Last modified: 2018/04/13 13:24 by Kalle Valo