From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: "Jonathan Corbet" <corbet@lwn.net>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/1] A small fix for parse-headers.rst
Date: Tue, 11 Nov 2025 17:25:10 +0100 [thread overview]
Message-ID: <cover.1762878176.git.mchehab+huawei@kernel.org> (raw)
Hi Jon,
This was supposed to be part of v4 of
https://lore.kernel.org/linux-doc/87ms4ty8ni.fsf@trenco.lwn.net/,
but it ended I didn't merge it, as I forgot to use "-a" on git commit...
Mauro Carvalho Chehab (1):
docs: parse-headers.rst: remove uneeded parenthesis
Documentation/doc-guide/parse-headers.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.51.1
next reply other threads:[~2025-11-11 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 16:25 Mauro Carvalho Chehab [this message]
2025-11-11 16:25 ` [PATCH 1/1] docs: parse-headers.rst: remove uneeded parenthesis Mauro Carvalho Chehab
2025-11-13 16:35 ` Jonathan Corbet
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=cover.1762878176.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@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;
as well as URLs for NNTP newsgroup(s).