All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manuel Ebner <manuelebnerli@mailbox.org>
To: Jonathan Corbet <corbet@lwn.net>, Shuah Khan <skhan@linuxfoundation.org>
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] Docs: software-requirements.rst: add lzop, lzma and ip-route2
Date: Thu, 13 Aug 2026 09:47:10 +0200	[thread overview]
Message-ID: <760d33b80873a2d62c72c54cd7abbdb77505cfb6.camel@mailbox.org> (raw)
In-Reply-To: <20260812122149.1635408-2-manuelebnerli@mailbox.org>

On Wed, 2026-08-12 at 14:21 +0200, Manuel Ebner wrote:
> lzma is required with HAVE_KERNEL_LZMA set to y
> lzop is required with CRYPTO_LZO set to y
> ip-route2 is mentioned in software-requirements below.
> 
> add tools to
>  software-requirements.rst
>  ver_linux
> 
> Signed-off-by: Manuel Ebner <manuelebnerli@mailbox.org>
> ---
>  Documentation/process/software-requirements.rst | 4 ++++
>  scripts/ver_linux                               | 4 ++++
>  2 files changed, 8 insertions(+)
> 
> diff --git a/Documentation/process/software-requirements.rst b/Documentation/process/software-requirements.rst
> index 69d31a3b5be3..5fdfcf6a0c01 100644
> --- a/Documentation/process/software-requirements.rst
> +++ b/Documentation/process/software-requirements.rst
> @@ -47,9 +47,12 @@ GNU make               4.0              make --version
>  [...]
> +ip-route2              6.14.0           ip -V
>  [...]
> +liblzma                5.8.1            lzma -V
> +lzop                   1.04             lzop -V
>  [...]
> +xz                     5.8.1            xz -V

Is this ok in one patch or should it be split up in one tool(set) per patch?
I will probably add tools for [v2].
syslinux (6.04) and genisoimage (1.1.11) so far.

I just took the version number of my system, but it's not the way to do this.
I'm open to suggestions for the version numbers itself or for a approach in general.

Thanks
 Manuel

>  [...]

  parent reply	other threads:[~2026-08-13  7:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-12 12:08 [PATCH 0/5] Docs: changes.rst: Rework Manuel Ebner
2026-08-12 12:14 ` [PATCH 1/5] Docs: changes.rst: rename file and references and add links Manuel Ebner
2026-08-12 12:35   ` sashiko-bot
2026-08-12 13:07   ` bot+bpf-ci
2026-08-12 13:15   ` Jonathan Corbet
2026-08-13  0:05     ` Randy Dunlap
2026-08-12 12:19 ` [PATCH 2/5] Docs: software-requirements.rst: Refine language Manuel Ebner
2026-08-13  0:03   ` Randy Dunlap
2026-08-12 12:21 ` [PATCH 3/5] Docs: software-requirements.rst: add lzop, lzma and ip-route2 Manuel Ebner
2026-08-13  0:04   ` Randy Dunlap
2026-08-13  7:47   ` Manuel Ebner [this message]
2026-08-12 12:22 ` [PATCH 4/5] Docs: pt_BR, it_IT: software-requirements.rst: copy tables from source Manuel Ebner
2026-08-12 12:24 ` [PATCH 5/5] Docs: software-requirements.rst replace optional tag with footnotes Manuel Ebner
2026-08-13  0:02   ` Randy Dunlap
2026-08-13  0:11   ` John Hubbard
2026-08-13 13:15   ` Jonathan Corbet
2026-08-13 14:30     ` Manuel Ebner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=760d33b80873a2d62c72c54cd7abbdb77505cfb6.camel@mailbox.org \
    --to=manuelebnerli@mailbox.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=workflows@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.