From: Simon Horman <horms@kernel.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Networking <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Kees Cook <kees@kernel.org>
Subject: Re: [PATCH net-next v2 2/3] net: dns_resolver: Move dns_query() explanation out of code block
Date: Thu, 25 Sep 2025 10:09:10 +0100 [thread overview]
Message-ID: <20250925090910.GZ836419@horms.kernel.org> (raw)
In-Reply-To: <20250924020626.17073-3-bagasdotme@gmail.com>
On Wed, Sep 24, 2025 at 09:06:24AM +0700, Bagas Sanjaya wrote:
> Documentation for dns_query() is placed in the function's literal code
> block snippet instead. Move it out of there.
>
> Fixes: 9dfe1361261b ("docs: networking: convert dns_resolver.txt to ReST")
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2025-09-25 9:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 2:06 [PATCH net-next v2 0/3] dns_resolver docs formatting cleanup Bagas Sanjaya
2025-09-24 2:06 ` [PATCH net-next v2 1/3] net: dns_resolver: Use reST bullet list for features list Bagas Sanjaya
2025-09-24 2:06 ` [PATCH net-next v2 2/3] net: dns_resolver: Move dns_query() explanation out of code block Bagas Sanjaya
2025-09-25 9:09 ` Simon Horman [this message]
2025-09-24 2:06 ` [PATCH net-next v2 3/3] net: dns_resolver: Fix request-key cross-reference Bagas Sanjaya
2025-09-26 22:30 ` [PATCH net-next v2 0/3] dns_resolver docs formatting cleanup patchwork-bot+netdevbpf
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=20250925090910.GZ836419@horms.kernel.org \
--to=horms@kernel.org \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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 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.