[PATCH v3 0/2] workflow, scripts: sort changes.rst and ver_linux

[PATCH v3 0/2] workflow, scripts: sort changes.rst and ver_linux

[Manuel Ebner]

It is a pain in the ass to compare the software versions on the running
system (scripts/ver_linux) with the minimal required versions (changes.rst).
Sorting both lists the same way makes side-by-side comparisons a simple task.

 [v2] -> [v3]:
fix changelog
changes.rst:
 needn't -> do not need to
 add gdb 7.2
ver_linux:
 /Changes.rst -> /changes.rst
 add gdb

 [v1] -> [v2]:
split v1 into a patch series
changes.rst:
 add reference to ver_linux
ver_linux:
 fix path to changes.rst

Signed-off-by: Manuel Ebner <manuelebner@airmail.cc>

[PATCH v3 1/2] workflow: process/changes.rst: sort and cleanup list

[Manuel Ebner]

It is a pain in the ass to compare the software versions on the running
system with the minimal required versions (process/changes.rst).
Sorting both lists the same way makes side-by-side comparisons a simple task.

add gdb version 7.2 as mentioned in:
 Documentation/process/debugging/gdb-kernel-debugging.rst
 scripts/gdb/vmlinux-gdb.py

sort table of required software versions alphabetically
add reference to scripts/ver_linux
needn't -> do not need to

Signed-off-by: Manuel Ebner <manuelebner@airmail.cc>
---
 Documentation/process/changes.rst | 54 ++++++++++++++++---------------
 1 file changed, 28 insertions(+), 26 deletions(-)

diff --git a/Documentation/process/changes.rst b/Documentation/process/changes.rst
index 6b373e193548..41c97163e67e 100644
--- a/Documentation/process/changes.rst
+++ b/Documentation/process/changes.rst
@@ -24,45 +24,47 @@ running, the suggested command should tell you.
 Again, keep in mind that this list assumes you are already functionally
 running a Linux kernel.  Also, not all tools are necessary on all
 systems; obviously, if you don't have any PC Card hardware, for example,
-you probably needn't concern yourself with pcmciautils.
+you probably do not need to concern yourself with pcmciautils. For a list of the
+programs on your system including their version execute ./scripts/ver_linux
 
 ====================== ===============  ========================================
         Program        Minimal version       Command to check the version
 ====================== ===============  ========================================
-GNU C                  8.1              gcc --version
-Clang/LLVM (optional)  15.0.0           clang --version
-Rust (optional)        1.78.0           rustc --version
-bindgen (optional)     0.65.1           bindgen --version
-GNU make               4.0              make --version
 bash                   4.2              bash --version
+bc                     1.06.95          bc --version
+bindgen (optional)     0.65.1           bindgen --version
 binutils               2.30             ld -v
-flex                   2.5.35           flex --version
 bison                  2.0              bison --version
-pahole                 1.22             pahole --version
-util-linux             2.10o            mount --version
-kmod                   13               depmod -V
+btrfs-progs            0.18             btrfs --version
+Clang/LLVM (optional)  15.0.0           clang --version
 e2fsprogs              1.41.4           e2fsck -V
+flex                   2.5.35           flex --version
+gdb                    7.2              gdb --version
+GNU AWK (optional)     5.1.0            gawk --version
+GNU C                  8.1              gcc --version
+GNU make               4.0              make --version
+GNU tar                1.28             tar --version
+grub                   0.93             grub --version || grub-install --version
+gtags (optional)       6.6.5            gtags --version
+iptables               1.4.2            iptables -V
 jfsutils               1.1.3            fsck.jfs -V
-xfsprogs               2.6.0            xfs_db -V
-squashfs-tools         4.0              mksquashfs -version
-btrfs-progs            0.18             btrfs --version
+kmod                   13               depmod -V
+mcelog                 0.6              mcelog --version
+mkimage (optional)     2017.01          mkimage --version
+nfs-utils              1.0.5            showmount --version
+openssl & libcrypto    1.0.0            openssl version
+pahole                 1.22             pahole --version
 pcmciautils            004              pccardctl -V
-quota-tools            3.09             quota -V
 PPP                    2.4.0            pppd --version
-nfs-utils              1.0.5            showmount --version
 procps                 3.2.0            ps --version
-udev                   081              udevd --version
-grub                   0.93             grub --version || grub-install --version
-mcelog                 0.6              mcelog --version
-iptables               1.4.2            iptables -V
-openssl & libcrypto    1.0.0            openssl version
-bc                     1.06.95          bc --version
-Sphinx\ [#f1]_         3.4.3            sphinx-build --version
-GNU tar                1.28             tar --version
-gtags (optional)       6.6.5            gtags --version
-mkimage (optional)     2017.01          mkimage --version
 Python                 3.9.x            python3 --version
-GNU AWK (optional)     5.1.0            gawk --version
+quota-tools            3.09             quota -V
+Rust (optional)        1.78.0           rustc --version
+Sphinx\ [#f1]_         3.4.3            sphinx-build --version
+squashfs-tools         4.0              mksquashfs -version
+udev                   081              udevadm --version
+util-linux             2.10o            mount --version
+xfsprogs               2.6.0            xfs_db -V
 ====================== ===============  ========================================
 
 .. [#f1] Sphinx is needed only to build the Kernel documentation
-- 
2.53.0

Re: [PATCH v3 0/2] workflow, scripts: sort changes.rst and ver_linux

[Jonathan Corbet]

Manuel Ebner <manuelebner@airmail.cc> writes:

> It is a pain in the ass to compare the software versions on the running
> system (scripts/ver_linux) with the minimal required versions (changes.rst).
> Sorting both lists the same way makes side-by-side comparisons a simple task.
>
>  [v2] -> [v3]:
> fix changelog
> changes.rst:
>  needn't -> do not need to
>  add gdb 7.2
> ver_linux:
>  /Changes.rst -> /changes.rst
>  add gdb

Please explain to me:

- Why I am getting multiple copies of the same patches

- Why I'm getting the same series from a completely different identity;
  the first set came from "Hans Anda"

- Why my request to separate out the logically different changes were
  ignored.

Thanks,

jon

Re: [PATCH v3 0/2] workflow, scripts: sort changes.rst and ver_linux

[Jonathan Corbet]

Manuel <manuelebner@airmail.cc> writes:

>> - Why I'm getting the same series from a completely different identity;
>>   the first set came from "Hans Anda"
>
> I messed this up, let me explain:
> I used to keep my real name out of the internet. The last couple days i changed
> my mind. I guess it's ok when my real name shows up in git blame.
> I really should have added a note about that. sorry.

So you sent me patches under a false name?  That's ... not the best way
to start building trust.

>> - Why my request to separate out the logically different changes were
>>   ignored.
>
> I split the patch into a series like i responded on Tue, 24 Feb 2026 08:13:02 
>>>i will make a Patch series with the files split.
>
> Do you want me to send two patches, which are not in a patch series?

No, I want you to separate the logical changes.

- Sorting the entries in the list is one logical change.

- Adding new items is a different one.  If you mix it in with the sort,
  nobody can really see which items are new.

See what I'm getting at?

jon

Re: [PATCH v3 0/2] workflow, scripts: sort changes.rst and ver_linux

[Manuel]

On Tue, 2026-03-03 at 12:27 -0700, Jonathan Corbet wrote:
> 
> > > - Why my request to separate out the logically different changes were
> > >   ignored.
> > 
> > I split the patch into a series like i responded on Tue, 24 Feb 2026
> > 08:13:02 
> > > > i will make a Patch series with the files split.
> > 
> > Do you want me to send two patches, which are not in a patch series?
> 
> No, I want you to separate the logical changes.
> 
> - Sorting the entries in the list is one logical change.
> 
> - Adding new items is a different one.  If you mix it in with the sort,
>   nobody can really see which items are new.

so I got that. I have a follow-up question.

should i make two or four patches?

[PATCH 1/2] ver_linux and changes.rst: addition and changes
[PATCH 2/2] ver_linux and changes.rst: sort

[PATCH 1/4] ver_linux: addition and changes
[PATCH 2/4] changes.rst: addition and changes
[PATCH 3/4] ver_linux: sort
[PATCH 4/4] changes.rst sort

Manuel