From: Simon Horman <horms@kernel.org>
To: Bharath SM <bharathsm.hsk@gmail.com>
Cc: davem@davemloft.net, dhowells@redhat.com, edumazet@google.com,
kuba@kernel.org, linux-doc@vger.kernel.org,
netdev@vger.kernel.org, corbet@lwn.net, pabeni@redhat.com,
Bharath SM <bharathsm@microsoft.com>
Subject: Re: [PATCH] dns_resolver: correct sysfs path name in dns resolver documentation
Date: Sat, 23 Mar 2024 16:29:56 +0000 [thread overview]
Message-ID: <20240323162956.GB403975@kernel.org> (raw)
In-Reply-To: <20240323081140.41558-1-bharathsm@microsoft.com>
On Sat, Mar 23, 2024 at 01:41:40PM +0530, Bharath SM wrote:
> Fix an incorrect sysfs path in dns resolver documentation
>
> Signed-off-by: Bharath SM <bharathsm@microsoft.com>
Hi,
There is another instance of "dnsresolver" in the same file.
Should it also be changed?
> ---
> Documentation/networking/dns_resolver.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/networking/dns_resolver.rst b/Documentation/networking/dns_resolver.rst
> index add4d59a99a5..99bf72a6ed45 100644
> --- a/Documentation/networking/dns_resolver.rst
> +++ b/Documentation/networking/dns_resolver.rst
> @@ -152,4 +152,4 @@ Debugging
> Debugging messages can be turned on dynamically by writing a 1 into the
> following file::
>
> - /sys/module/dnsresolver/parameters/debug
> + /sys/module/dns_resolver/parameters/debug
> --
> 2.34.1
>
>
next prev parent reply other threads:[~2024-03-23 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-23 8:11 [PATCH] dns_resolver: correct sysfs path name in dns resolver documentation Bharath SM
2024-03-23 16:29 ` Simon Horman [this message]
2024-03-24 10:48 ` Bharath SM
2024-03-24 10:43 ` [PATCH v2] dns_resolver: correct module " Bharath SM
2024-03-25 17:17 ` Simon Horman
2024-03-26 9:24 ` 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=20240323162956.GB403975@kernel.org \
--to=horms@kernel.org \
--cc=bharathsm.hsk@gmail.com \
--cc=bharathsm@microsoft.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.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.