Linux Kernel: Mining for Maintainers
I am interested in the Mining Maintainers mentorship program and I would like to work on the tasks for the mentee selection.
_______________________________________________
Linux-kernel-mentees mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
Quoted 3 lines · Piyush Thange
I am interested in the Mining Maintainers mentorship program and I would like to work on the tasks for the mentee selection.
The zeroth task is to learn suitable netiquette for the communication with the kernel community. Below are some basic rules and pointers for this mentorship. More information on kernel netiquette is also at
https://people.kernel.org/tglx/notes-about-netiquette.
First, please do not top-post.
A: Because we read from top to bottom, left to right.
Q: Why should I start my reply below the quoted text?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: The lost context.
Q: What makes top-posted replies harder to read than bottom-posted?
A: Yes.
Q: Should I trim down the quoted part of an email to which I'm replying?
Second, please always CC: [email protected].
Third, set up your email client according to the kernel community rules. Here is some information to that:
https://www.kernel.org/doc/html/latest/process/submitting-patches.html#no-mime-no-links-no-compression-no-attachments-just-plain-text
https://www.kernel.org/doc/html/latest/process/email-clients.html
Generally more information on submitting patches and responding on replies is at https://www.kernel.org/doc/html/latest/process/submitting-patches.html
Once the zeroth task is understood, you can now move on to the first task:
First, download the kernel git repository and compile the kernel with the x86-defconfig build configuration.
There is a file called MAINTAINERS in the root directory of the git repository. Read the introduction at the beginning of the MAINTAINERS file and understand the content in the file and its organisation.
Explain in your words: What is stored in the MAINTAINERS file?
Now, search for specific MAINTAINER entries; Please answer: Who are the maintainers and reviewers of the following sections?
DVB_USB_GL861 MEDIA DRIVER
FREESCALE USB PHY DRIVER
HYPERBUS SUPPORT
I2C-TINY-USB DRIVER
IMON SOUNDGRAPH USB IR RECEIVER
INTEL PRO/WIRELESS 2100, 2200BG, 2915ABG NETWORK CONNECTION SUPPORT NVM EXPRESS DRIVER
PS3VRAM DRIVER
PWM FAN DRIVER
UNSORTED BLOCK IMAGES (UBI)
Please let us know about your answers and always send your responses to the linux-kernel-mentees mailing list. After that first exercise, exercises 2 and 3 will follow.
Best regards,
Lukas
_______________________________________________
Linux-kernel-mentees mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
Quoted 60 lines · Lukas Bulwahn
Quoted 3 lines · Piyush Thange
I am interested in the Mining Maintainers mentorship program and I would like to work on the tasks for the mentee selection.
The zeroth task is to learn suitable netiquette for the communication with the kernel community. Below are some basic rules and pointers for this mentorship. More information on kernel netiquette is also at
https://people.kernel.org/tglx/notes-about-netiquette.First, please do not top-post.
A: Because we read from top to bottom, left to right.
Q: Why should I start my reply below the quoted text?A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?A: The lost context.
Q: What makes top-posted replies harder to read than bottom-posted?A: Yes.
Q: Should I trim down the quoted part of an email to which I'm replying?Second, please always CC: [email protected].
Third, set up your email client according to the kernel community rules. Here is some information to that:
https://www.kernel.org/doc/html/latest/process/submitting-patches.html#no-mime-no-links-no-compression-no-attachments-just-plain-text
https://www.kernel.org/doc/html/latest/process/email-clients.htmlGenerally more information on submitting patches and responding on replies is at https://www.kernel.org/doc/html/latest/process/submitting-patches.html
Once the zeroth task is understood, you can now move on to the first task:
First, download the kernel git repository and compile the kernel with the x86-defconfig build configuration.
There is a file called
MAINTAINERSin the root directory of the git repository. Read the introduction at the beginning of theMAINTAINERSfile and understand the content in the file and its organisation.Explain in your words: What is stored in the
MAINTAINERSfile?Now, search for specific MAINTAINER entries; Please answer: Who are the maintainers and reviewers of the following sections?
DVB_USB_GL861MEDIA DRIVER
FREESCALE USB PHY DRIVER
HYPERBUS SUPPORT
I2C-TINY-USB DRIVER
IMON SOUNDGRAPH USB IR RECEIVER
INTEL PRO/WIRELESS 2100, 2200BG, 2915ABG NETWORK CONNECTION SUPPORT NVM EXPRESS DRIVER
PS3VRAM DRIVER
PWM FAN DRIVER
UNSORTED BLOCK IMAGES (UBI)
Quoted 9 lines
Please let us know about your answers and always send your responses to the linux-kernel-mentees mailing list. After that first exercise, exercises 2 and 3 will follow.
Best regards,
Lukas
Greetings,
I've compiled the mainline kernel using defconfig.
------------------------------------------------------------------------------
**What's stored in the MAINTAINERS file?**
The MAINTAINERS file contains the information for patch submitter and the rules to be followed by them. There are basically 7 tips to be followed. The first two tips cover the testing of a patch and getting it reviewed by people.
The next two cover the compilation of changes made by the developer and make them available for testing purpose.
The fifth tip is one of the important where a submitter need to check the formatting style for the code using script ``checkpatch.pl`` & get the maintainer for the patch using script ``get_maintainer.pl``.
The inclusion of Sign is must.
The next two tips contains the authority of a patch and
sending it to related maintainer.
Next are the descriptions assigned to section entries which are used further for providing the information about the Maintainer, Reviewer, Status, SCM and so on.
eg. M: Maintainers
R: Reviewers
------------------------------------------------------------------------------
**Below is the list for the Maintainers & Reviewers.**
DVB_USB_GL861 MEDIA DRIVER
M: Antti Palosaari <[email protected]>
FREESCALE USB PHY DRIVER
M: Ran Wang <[email protected]>
HYPERBUS SUPPORT
M: Vignesh Raghavendra <[email protected]>
I2C-TINY-USB DRIVER
M: Till Harbaum <[email protected]>
IMON SOUNDGRAPH USB IR RECEIVER
M: Sean Young <[email protected]>
INTEL PRO/WIRELESS 2100, 2200BG, 2915ABG NETWORK CONNECTION SUPPORT
M: Stanislav Yakovlev <[email protected]>
NVM EXPRESS DRIVER
M: Keith Busch <[email protected]>
M: Jens Axboe <[email protected]>
M: Christoph Hellwig <[email protected]>
M: Sagi Grimberg <[email protected]>
PS3VRAM DRIVER
M: Jim Paris <[email protected]>
M: Geoff Levand <[email protected]>
PWM FAN DRIVER
M: Bartlomiej Zolnierkiewicz <[email protected]>
UNSORTED BLOCK IMAGES (UBI)
M: Richard Weinberger <[email protected]>
-------------------------------------------------------------------------------
Regards,
Piyush T.
_______________________________________________
Linux-kernel-mentees mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees