From: Max Staudt <max@enpas.org>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: Wolfgang Grandegger <wg@grandegger.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-can@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] can: can327: Fix a broken link to Documentation
Date: Sun, 31 Jul 2022 10:44:52 +0200 [thread overview]
Message-ID: <20220731104452.3bc2e76c.max@enpas.org> (raw)
In-Reply-To: <6a54aff884ea4f84b661527d75aabd6632140715.1659249135.git.christophe.jaillet@wanadoo.fr>
Thanks, Christophe!
Max
On Sun, 31 Jul 2022 08:32:52 +0200
Christophe JAILLET <christophe.jaillet@wanadoo.fr> wrote:
> Since commit 482a4360c56a ("docs: networking: convert netdevices.txt to
> ReST"), Documentation/networking/netdevices.txt has been replaced by
> Documentation/networking/netdevices.rst.
>
> Update the comment accordingly to avoid a 'make htmldocs' warning
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
> drivers/net/can/can327.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/can/can327.c b/drivers/net/can/can327.c
> index 5da7778d92dc..925e880bf570 100644
> --- a/drivers/net/can/can327.c
> +++ b/drivers/net/can/can327.c
> @@ -827,7 +827,7 @@ static netdev_tx_t can327_netdev_start_xmit(struct sk_buff *skb,
> netif_stop_queue(dev);
>
> /* BHs are already disabled, so no spin_lock_bh().
> - * See Documentation/networking/netdevices.txt
> + * See Documentation/networking/netdevices.rst
> */
> spin_lock(&elm->lock);
> can327_send_frame(elm, frame);
next prev parent reply other threads:[~2022-07-31 8:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 6:32 [PATCH] can: can327: Fix a broken link to Documentation Christophe JAILLET
2022-07-31 8:44 ` Max Staudt [this message]
2022-07-31 18:52 ` Marc Kleine-Budde
2022-07-31 18:54 ` Marc Kleine-Budde
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=20220731104452.3bc2e76c.max@enpas.org \
--to=max@enpas.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wg@grandegger.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