New Contributor

New Contributor

[Chris Lapa]

Hi,

I'm new to contributing to the kernel and am just wondering what the 
correct etiquette is for having my patches reviewed/accepted.

I have already sent in a small patch series for the max8903 battery 
charger (http://marc.info/?l=linux-pm&m=146484997909503&w=2).

Thanks,
Chris Lapa

Re: New Contributor

[Mason]

On 06/06/2016 06:09, Chris Lapa wrote:

> I'm new to contributing to the kernel and am just wondering what the
> correct etiquette is for having my patches reviewed/accepted.

This document provides some guidelines:
https://www.kernel.org/doc/Documentation/SubmittingPatches

The MAINTAINERS file is useful to figure out *who* to send patches to:
https://www.kernel.org/doc/linux/MAINTAINERS

Regards.

Re: New Contributor

[Krzysztof Kozlowski]

On Mon, Jun 6, 2016 at 10:40 AM, Mason <slash.tmp@free.fr> wrote:
> On 06/06/2016 06:09, Chris Lapa wrote:
>
>> I'm new to contributing to the kernel and am just wondering what the
>> correct etiquette is for having my patches reviewed/accepted.

Usually the etiquette for pinging/resending is to wait for two weeks.
Although I think it is not written anywhere explicitly.

>
> This document provides some guidelines:
> https://www.kernel.org/doc/Documentation/SubmittingPatches
>
> The MAINTAINERS file is useful to figure out *who* to send patches to:
> https://www.kernel.org/doc/linux/MAINTAINERS

A little bit easier it might be to use scripts/get_maintainer.pl.

In your case the DT bindings should get an ack from device tree folks
and you did not cc them. get_maintainer.pl will help you with that.

Best regards,
Krzysztof

new contributor

[souleymane conté]

[-- Attachment #1: Type: text/plain, Size: 671 bytes --]

Hi,
I am interested in contributing to the QEMU project. I would like to begin
by working on the task described in Issue #527 on GitLab:
https://gitlab.com/qemu-project/qemu/-/issues/527.

The task involves Plain text files in docs/ should be converted to rst:
- docs/igd-assign.txt
- docs/image-fuzzer.txt
I would appreciate it if you could confirm that this task is still
available to work on. Once confirmed, I will proceed with preparing and
submitting patches as per the QEMU patch submission guidelines.

Thank you for your time and for maintaining such an important project. I
look forward to contributing.

Best regards,
Souleymane CONTE
GitLab Username: soconte

[-- Attachment #2: Type: text/html, Size: 872 bytes --]

Re: new contributor

[Peter Maydell]

On Fri, 2 May 2025 at 09:52, souleymane conté
<conte.souleymane@gmail.com> wrote:
> I am interested in contributing to the QEMU project. I would like
> to begin by working on the task described in Issue #527 on GitLab:
> https://gitlab.com/qemu-project/qemu/-/issues/527.
>
> The task involves Plain text files in docs/ should be converted to rst:
>
> docs/igd-assign.txt
> docs/image-fuzzer.txt
>
>
> I would appreciate it if you could confirm that this task is still available to work on.

Hi; yes, this task is still available to work on. We've been
gradually converting the remaining text files in docs/ to RST,
but there are still some left, including the two you list.

I would note that as we've done the conversions we've mostly
done the easier ones first, so the files that are left are
getting a bit trickier to do. In particular, anything in docs/
needs not just to be converted in format, but also it needs
to live in the correct sub-part of the manual (system/,
devel/, interop/, etc), and sometimes a single txt file
combines information that needs to be split into several
different places.

If you don't mind which docs you're looking at, these two
are simple format conversions that are already in the right
place in the manual and don't need splitting up:
  docs/interop/qcow2.txt
  docs/interop/qed_spec.txt
(You can look at other files in that directory and at the commits
in the git history that converted them from txt to rst to get
ideas on how to handle some of the things like ASCII art diagrams
and tables.)

Of the two files you list, I think docs/image-fuzzer.txt can
probably reasonably become docs/devel/image-fuzzer.rst without
needing to be split up. docs/igd-assign.txt is a bit trickier,
but I think most of the content belongs somewhere under system/.

thanks
-- PMM