From: Bruno Moreira-Guedes <codeagain@codeagain.dev>
To: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
outreachy@lists.linux.dev,
Bruno's Patch Watchbox <patch-reply@codeagain.dev>
Subject: [PATCH 2/2] Docs: Update kernel series in changes.rst
Date: Mon, 18 Apr 2022 23:58:35 -0300 [thread overview]
Message-ID: <a124c3c34e627c124673640aed177c10e401b052.1650336366.git.codeagain@codeagain.dev> (raw)
In-Reply-To: <cover.1650336366.git.codeagain@codeagain.dev>
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
The file 'Documentation/process/changes.rst' states the listed
requirements are for the 4.x kernel version. However, there are
requirements updated for the 5.x version, so this patch updates it to
match the current kernel version.
Signed-off-by: Bruno Moreira-Guedes <codeagain@codeagain.dev>
---
Documentation/process/changes.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/process/changes.rst b/Documentation/process/changes.rst
index 41a44e5f47e6..08515b11cf92 100644
--- a/Documentation/process/changes.rst
+++ b/Documentation/process/changes.rst
@@ -7,7 +7,7 @@ Intro
=====
This document is designed to provide a list of the minimum levels of
-software necessary to run the 4.x kernels.
+software necessary to run the 5.x kernels.
This document is originally based on my "Changes" file for 2.0.x kernels
and therefore owes credit to the same people as that file (Jared Mauch,
--
2.35.3
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-04-19 2:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 2:57 [PATCH 0/2] Docs: Update information at changes.rst Bruno Moreira-Guedes
2022-04-19 2:57 ` [PATCH 1/2] Docs: Add cpio requirement to changes.rst Bruno Moreira-Guedes
2022-04-19 2:58 ` Bruno Moreira-Guedes [this message]
2022-04-19 3:06 ` [PATCH 2/2] Docs: Update kernel series in changes.rst Matthew Wilcox
2022-04-19 12:53 ` Bruno Moreira-Guedes
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=a124c3c34e627c124673640aed177c10e401b052.1650336366.git.codeagain@codeagain.dev \
--to=codeagain@codeagain.dev \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy@lists.linux.dev \
--cc=patch-reply@codeagain.dev \
/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;
as well as URLs for NNTP newsgroup(s).