From:   Jonathan Corbet <corbet@lwn.net>
To:     Tomasz =?utf-8?B?V2FybmllxYLFgm8=?= <tomasz.warniello@gmail.com>
Cc:     Jani Nikula <jani.nikula@linux.intel.com>,
        linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts: kernel-doc: transform documentation into POD
In-Reply-To: <20220103224806.2932bac2@fuji.fritz.box>
References: <20211209225549.69010-1-tomasz.warniello@gmail.com>
 <87h7b8cfg0.fsf@meer.lwn.net>
 <0796a780-f5ee-0b6c-e7ef-544ba5f6a429@gmail.com>
 <87pmp9tcju.fsf@intel.com> <20220103183034.77ba8a8c@fuji.fritz.box>
 <87bl0sziva.fsf@meer.lwn.net> <20220103224806.2932bac2@fuji.fritz.box>
Date:   Mon, 03 Jan 2022 14:57:48 -0700
Message-ID: <8735m4zdlv.fsf@meer.lwn.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

Tomasz Warnie=C5=82=C5=82o <tomasz.warniello@gmail.com> writes:

>>  - Post your patch series as a single thread with a coherent cover
>>    letter.
>
> Sorry, I'm a newbie in this business. I need to figure out how emails
> work. Is this just one thread per version or one thread per all versions?
> Can you please direct me to some documentation about this?

One thread per version is good; please do not post new versions to old
threads.  A tool like "git send-email" can be your friend here.  See
Documentation/process/submitting-patches.rst for lots of details on how
to submit patches.

Along these lines, I appreciate that you broke up the series as I
requested, but you overdid it a bit.  Think in terms of logical changes
and making things easy to review, and you should be able to coalesce
things a bit.

>>  - Stick with current coding conventions
>
> To be honest, I need to think this over.

Think hard; if you're unable to work with the kernel project's
conventions, there's not a lot of point in resubmitting the patches.=20

Thanks,

jon