From mboxrd@z Thu Jan 1 00:00:00 1970 From: mchehab at kernel.org (Mauro Carvalho Chehab) Date: Thu, 27 Jun 2019 06:48:33 -0300 Subject: [Linux-kernel-mentees] Patch guidelines and tips In-Reply-To: <6aa42000-1957-b0cf-ae6d-18e89d304892@linuxfoundation.org> References: <6aa42000-1957-b0cf-ae6d-18e89d304892@linuxfoundation.org> Message-ID: <20190627064833.3e41d60a@coco.lan> List-Id: Em Wed, 26 Jun 2019 18:38:31 -0600 Shuah Khan escreveu: > Mentees, > > Thanks for your active participation in working towards the > required contributions. A few tips and guidelines to make > this experience productive for us all. > > - Before you start working on a task, please check the archive > first to see if a patch is already in progress. This avoids > duplicated efforts. > > https://lists.linuxfoundation.org/pipermail/linux-kernel-mentees/ > > - For documentation tasks, start small with picking one file for > conversion first. You don't have to work on all the files in a > directory in one step. Working on a single file helps you get > over the learning curve and then you can take on larger set of > files as needed. > > If in doubt, send email to maintainers - starting with me if you > prefer. Please feel free to send e-mail to me with regards to documentation tasks. I'm open to help with that. Also, I have a big series of documentation patches under discussion for the merge process. So, better to check with me before trying to work on something that was already done. > > These steps are all documented on the project page. Don't forget to > do the following when you send patches: > > - Please copy mailing lists and maintainers/developers suggested by > scripts/get_maintainer.pl > > - Please run scripts/checkpatch.pl before sending the patch. > > - Compile and test - Documentation compile steps have been documented. > > thanks, > -- Shuah > > > > Thanks, Mauro From mboxrd@z Thu Jan 1 00:00:00 1970 From: mchehab@kernel.org (Mauro Carvalho Chehab) Date: Thu, 27 Jun 2019 06:48:33 -0300 Subject: [Linux-kernel-mentees] Patch guidelines and tips In-Reply-To: <6aa42000-1957-b0cf-ae6d-18e89d304892@linuxfoundation.org> References: <6aa42000-1957-b0cf-ae6d-18e89d304892@linuxfoundation.org> Message-ID: <20190627064833.3e41d60a@coco.lan> List-Id: Content-Type: text/plain; charset="UTF-8" Message-ID: <20190627094833.oI6uKAqq8VfROe22tNllAGBokhMJLIpVLuhs7mklKzw@z> Em Wed, 26 Jun 2019 18:38:31 -0600 Shuah Khan escreveu: > Mentees, > > Thanks for your active participation in working towards the > required contributions. A few tips and guidelines to make > this experience productive for us all. > > - Before you start working on a task, please check the archive > first to see if a patch is already in progress. This avoids > duplicated efforts. > > https://lists.linuxfoundation.org/pipermail/linux-kernel-mentees/ > > - For documentation tasks, start small with picking one file for > conversion first. You don't have to work on all the files in a > directory in one step. Working on a single file helps you get > over the learning curve and then you can take on larger set of > files as needed. > > If in doubt, send email to maintainers - starting with me if you > prefer. Please feel free to send e-mail to me with regards to documentation tasks. I'm open to help with that. Also, I have a big series of documentation patches under discussion for the merge process. So, better to check with me before trying to work on something that was already done. > > These steps are all documented on the project page. Don't forget to > do the following when you send patches: > > - Please copy mailing lists and maintainers/developers suggested by > scripts/get_maintainer.pl > > - Please run scripts/checkpatch.pl before sending the patch. > > - Compile and test - Documentation compile steps have been documented. > > thanks, > -- Shuah > > > > Thanks, Mauro