From 5a5c6be7c332451877ab7b2e6078d7aa6ab1adb2 Mon Sep 17 00:00:00 2001 From: Mahdi Dibaiee Date: Sat, 27 Nov 2021 11:46:58 +0000 Subject: [PATCH] Guidelines for creating the patch --- _posts/2021-11-06-linux-contribution.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/_posts/2021-11-06-linux-contribution.md b/_posts/2021-11-06-linux-contribution.md index 9cdb568..bf29948 100644 --- a/_posts/2021-11-06-linux-contribution.md +++ b/_posts/2021-11-06-linux-contribution.md @@ -179,6 +179,12 @@ And then, I can load this symbol file as well: (gdb) list *(recent_mt+0x167) {% endhighlight %}--> +# Creating your patch + +Here are some good guidelines on how to prepare and send your patch: +- [The perfect patch](https://www.ozlabs.org/~akpm/stuff/tpp.txt) +- [Linux kernel patch submission checklist](https://www.kernel.org/doc/html/v4.10/process/submit-checklist.html) + # What did I work on? The first issue I was interested in turned out to be an invalid bug: I found that out by investigating the script the user was testing and measuring how much time each part of the script took to find out the main culprit: [bug-214851](https://bugzilla.kernel.org/show_bug.cgi?id=214851). But I learned a lot during this alone, mostly about how to build things quickly, where to look for modules, how to enable debugging for them, etc.