This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
en:developers:documentation:submittingpatches [2019/06/23 09:10] Thomas Nagy [Use RFC or RFT for patches not ready] RFT typo |
en:developers:documentation:submittingpatches [2020/02/13 16:29] Kalle Valo Add Co-developed-by |
||
---|---|---|---|
Line 33: | Line 33: | ||
* [[en/users/drivers/ath10k/submittingpatches|ath10k]] | * [[en/users/drivers/ath10k/submittingpatches|ath10k]] | ||
+ | * [[en/users/drivers/ath11k/submittingpatches|ath11k]] | ||
===== Checking state of patches from patchwork ===== | ===== Checking state of patches from patchwork ===== | ||
Line 277: | Line 278: | ||
commit log message header line text enclosed in parentheses and | commit log message header line text enclosed in parentheses and | ||
double quotes with no line breaks whatsoever. | double quotes with no line breaks whatsoever. | ||
+ | The fixes lines must be placed just above the signed-off-by lines. | ||
Example: | Example: | ||
Line 361: | Line 363: | ||
If the patches are not yet ready to be applied by the maintainer, mark them as RFC (Request For Comments) or RFT (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. | If the patches are not yet ready to be applied by the maintainer, mark them as RFC (Request For Comments) or RFT (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. | ||
+ | ==== Use Co-developed-by when multiple authors ==== | ||
+ | |||
+ | When a patch has multiple authors you should use Co-developed-by tag: | ||
+ | |||
+ | https://www.kernel.org/doc/html/latest/process/submitting-patches.html#when-to-use-acked-by-cc-and-co-developed-by | ||
===== More references ===== | ===== More references ===== |