Re: [PATCH] checkpatch: allow tags between co-developed-by and their sign-off

Hi Przemek, On Mon, Oct 23, 2023 at 12:29 PM Przemek Kitszel wrote: > > Allow additional tags between Co-developed-by: and Signed-off-by:. > > Removing the "immediately" word from the doc is a great summary of the > change - there is no need for the two tags to be glued together, barring > ease o

Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process

ne-learning AI to make some commits in the stable tree carrying a CVE identifier and some others not. Reviewed-by: Lukas Bulwahn Below, there is just some nitpicking on some wording: > Documentation/process/cve.rst | 120 > Documentation/process/index.rst

[PATCH] docs: submit-checklist: structure by category

o Randy to stay the first one in any reordering. While at it, the reference to CONFIG_SLUB_DEBUG was replaced by CONFIG_DEBUG_SLAB. Signed-off-by: Lukas Bulwahn --- So far, no point disappeared and nothing new was added. Points/Ideas for further improvements (based on my knowledge and judgement)

Re: [PATCH] docs: submit-checklist: structure by category

Hi Jani, On Mon, Feb 26, 2024 at 1:48 PM Jani Nikula wrote: > > On Mon, 26 Feb 2024, Lukas Bulwahn wrote: > > diff --git a/Documentation/process/submit-checklist.rst > > b/Documentation/process/submit-checklist.rst > > index b1bc2d37bd0a..7d8dba942fe8 100644 > &g

Re: [PATCH] docs: submit-checklist: structure by category

On Tue, Feb 27, 2024 at 1:41 AM Randy Dunlap wrote: > > Hi Lukas, > > I'll review the file changes separately. This is just replying > to the patch description comments. > > > On 2/26/24 02:46, Lukas Bulwahn wrote: (snipped) > > > Note that the previous fi

Re: [PATCH] docs: submit-checklist: structure by category

On Tue, Feb 27, 2024 at 9:57 AM Geert Uytterhoeven wrote: > > Hi Randy, > > On Tue, Feb 27, 2024 at 1:41 AM Randy Dunlap wrote: > > > - Concerning checking with tools, checkpatch probably still makes sense; > > > it pointed out in several places. If sparse and checkstack are really > > >

[PATCH v2-squashed] docs: submit-checklist: structure by category

Reviewed-by: Randy Dunlap Tested-by: Randy Dunlap Signed-off-by: Lukas Bulwahn --- Documentation/process/submit-checklist.rst | 163 +++-- 1 file changed, 88 insertions(+), 75 deletions(-) diff --git a/Documentation/process/submit-checklist.rst b/Documentation/process/submit

[PATCH v2 0/3] docs: submit-checklist: structure by category

s 'logically one change' to a single document. So, I also squashed the three patches back into one patch, sent out as PATCH v2-squashed: https://lore.kernel.org/linux-doc/20240229030146.8418-1-lukas.bulw...@gmail.com/ Please either pick this patch series or just the PATCH v2-squashed

[PATCH v2 1/3] docs: submit-checklist: structure by category

ll to keep 'include what you use' to be the first in the list. While at it, replace the reference to the obsolete CONFIG_DEBUG_SLAB with CONFIG_SLUB_DEBUG. Reviewed-by: Randy Dunlap Tested-by: Randy Dunlap Signed-off-by: Lukas Bulwahn --- Documentation/process/submit

[PATCH v2 2/3] docs: submit-checklist: use subheadings

://lore.kernel.org/linux-doc/87o7c3mlwb@intel.com/ Signed-off-by: Lukas Bulwahn --- Documentation/process/submit-checklist.rst | 26 -- 1 file changed, 14 insertions(+), 12 deletions(-) diff --git a/Documentation/process/submit-checklist.rst b/Documentation/process/submit

[PATCH v2 3/3] docs: submit-checklist: change to autonumbered lists

During review (see Link), Jani Nikula suggested to use autonumbered lists instead of manually-maintained bullet numbering. Turn all lists into autonumbered lists. Link: https://lore.kernel.org/linux-doc/87o7c3mlwb@intel.com/ Signed-off-by: Lukas Bulwahn --- Documentation/process/submit

Re: [PATCH v2 0/3] docs: submit-checklist: structure by category

On Thu, Feb 29, 2024 at 11:25 AM Jani Nikula wrote: > > On Thu, 29 Feb 2024, Lukas Bulwahn wrote: > > from Jani Nikula: > > - turn categories into subheadings > > - use common heading adornment > > - change to bullet or autonumbered lists > >

[PATCH 0/3] Towards a re-organized submitting patches

dy be accepted to be included upfront to lower the risks and conflicts when continuing the editorial work. Well, long text... some short simple patches for now. Best regards, Lukas Lukas Bulwahn (3): docs: submitting-patches: divert focus from PATCH in the subject line docs: submitti

[PATCH 1/3] docs: submitting-patches: divert focus from PATCH in the subject line

this note into 'the canonical patch format' section, where it currently fits best. Signed-off-by: Lukas Bulwahn --- Documentation/process/submitting-patches.rst | 14 -- 1 file changed, 4 insertions(+), 10 deletions(-) diff --git a/Documentation/process/submitting-patches.

[PATCH 2/3] docs: submitting-patches: move split_changes before describe_change

7;Describe your changes'. Note that this is also the order in 5.Posting. The same content is there covered in Patch preparation and Patch formatting. Signed-off-by: Lukas Bulwahn --- Documentation/process/submitting-patches.rst | 68 ++-- 1 file changed, 34 insertions(+), 3

[PATCH 3/3] docs: submitting-patches: move backtraces to patch description

into imperative form. Signed-off-by: Lukas Bulwahn --- Documentation/process/submitting-patches.rst | 47 +++- 1 file changed, 25 insertions(+), 22 deletions(-) diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst index 37925c

Re: [PATCH 0/3] Towards a re-organized submitting patches

On Sun, Mar 3, 2024 at 5:31 PM Jonathan Corbet wrote: > > Lukas Bulwahn writes: > > > Dear Jonathan, > > > > I wanted to clean up the development-process documentation. There is > > however no easy way to break the ice here: > > > > The elephant in th