From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Networking <netdev@vger.kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Kees Cook <kees@kernel.org>, Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH net-next 0/3] dns_resolver docs formatting cleanup
Date: Mon, 22 Sep 2025 16:56:45 +0700 [thread overview]
Message-ID: <20250922095647.38390-2-bagasdotme@gmail.com> (raw)
Hi,
Here are reST cleanups for DNS Resolver Module documentation. The shortlog
below should be self-explanatory.
Enjoy!
Bagas Sanjaya (3):
net: dns_resolver: Use reST bullet list for features list
net: dns_resolver: Move dns_query() explanation out of code block
net: dns_resolver: Fix request-key cross-reference
Documentation/networking/dns_resolver.rst | 53 +++++++++++------------
1 file changed, 26 insertions(+), 27 deletions(-)
base-commit: 312e6f7676e63bbb9b81e5c68e580a9f776cc6f0
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2025-09-22 9:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 9:56 Bagas Sanjaya [this message]
2025-09-22 9:56 ` [PATCH net-next 1/3] net: dns_resolver: Use reST bullet list for features list Bagas Sanjaya
2025-09-23 10:07 ` Simon Horman
2025-09-22 9:56 ` [PATCH net-next 2/3] net: dns_resolver: Move dns_query() explanation out of code block Bagas Sanjaya
2025-09-23 10:14 ` Simon Horman
2025-09-24 0:44 ` Bagas Sanjaya
2025-09-24 5:00 ` Randy Dunlap
2025-09-25 9:08 ` Simon Horman
2025-09-22 9:56 ` [PATCH net-next 3/3] net: dns_resolver: Fix request-key cross-reference Bagas Sanjaya
2025-09-23 10:23 ` Simon Horman
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=20250922095647.38390-2-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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).