From: Randy Dunlap <rdunlap@infradead.org>
To: Manuel Ebner <manuelebnerli@mailbox.org>,
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 v2] Docs/process/changes: add comment referring to ver_linux
Date: Sat, 21 Nov 2026 08:53:20 -0800 [thread overview]
Message-ID: <bd50aa92-fffe-4176-ba63-4812c68565f8@infradead.org> (raw)
In-Reply-To: <20261121115203.1444513-2-manuelebnerli@mailbox.org>
On 11/21/26 3:52 AM, Manuel Ebner wrote:
> Add comment to keep ver_linux up to date. This comment does not show up
> in the output of sphinx.
>
> Signed-off-by: Manuel Ebner <manuelebnerli@mailbox.org>
> ---
> [v2]
> fix typos in diff and subject
>
> [v1]
> https://lore.kernel.org/all/20261121113221.1442278-2-manuelebnerli@mailbox.org/
>
> Documentation/process/changes.rst | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/process/changes.rst b/Documentation/process/changes.rst
> index 13093c5c26..ffeaa3dce3 100644
> --- a/Documentation/process/changes.rst
> +++ b/Documentation/process/changes.rst
> @@ -27,6 +27,10 @@ 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 do not need to concern yourself with pcmciautils.
>
> +..
> + When changing anything in the following table, make sure to update
> + scripts/ver_linux aswell.
as well.
> +
> ====================== =============== ========================================
> Program Minimal version Command to check the version
> ====================== =============== ========================================
--
~Randy
prev parent reply other threads:[~2026-11-21 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-21 11:52 Manuel Ebner
2026-11-21 16:53 ` Randy Dunlap [this message]
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=bd50aa92-fffe-4176-ba63-4812c68565f8@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manuelebnerli@mailbox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®