linux-kernel - Re: [PATCH] scripts: kernel-doc: transform documentation into POD

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <8735m4zdlv.fsf@meer.lwn.net>
Date:   Mon, 03 Jan 2022 14:57:48 -0700
From:   Jonathan Corbet <corbet@....net>
To:     Tomasz Warniełło <tomasz.warniello@...il.com>
Cc:     Jani Nikula <jani.nikula@...ux.intel.com>,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] scripts: kernel-doc: transform documentation into POD

Tomasz Warniełło <tomasz.warniello@...il.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. 

Thanks,

jon