netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vincent MAILHOL <mailhol.vincent@wanadoo.fr>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	David Miller <davem@davemloft.net>,
	Networking <netdev@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: [PATCH] Documentation: devlink: add missing toc entry for etas_es58x devlink doc
Date: Tue, 13 Dec 2022 23:14:48 +0900	[thread overview]
Message-ID: <CAMZ6Rq+w3ZG5Y=6m+dFL_p3WLUFUkLKarj253nWu9q3+-GOH6Q@mail.gmail.com> (raw)
In-Reply-To: <20221213133954.f2msxale6a37bvvo@pengutronix.de>

On Tue. 13 Dec. 2022 at 22:39, Marc Kleine-Budde <mkl@pengutronix.de> wrote:
> On 13.12.2022 14:11:36, Vincent Mailhol wrote:
> > toc entry is missing for etas_es58x devlink doc and triggers this warning:
> >
> >   Documentation/networking/devlink/etas_es58x.rst: WARNING: document isn't included in any toctree
> >
> > Add the missing toc entry.
> >
> > Fixes: 9f63f96aac92 ("Documentation: devlink: add devlink documentation for the etas_es58x driver")
> > Signed-off-by: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
>
> Added to linux-can-next + added Reported-bys.

Thanks :)

FYI, I now have access to a build environment. I confirmed that this
patch fixes the warning.

Yours sincerely,
Vincent Mailhol

  reply	other threads:[~2022-12-13 14:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13  4:37 linux-next: build warning after merge of the net-next tree Stephen Rothwell
2022-12-13  5:11 ` [PATCH] Documentation: devlink: add missing toc entry for etas_es58x devlink doc Vincent Mailhol
2022-12-13  8:15   ` Marc Kleine-Budde
2022-12-13 13:39   ` Marc Kleine-Budde
2022-12-13 14:14     ` Vincent MAILHOL [this message]
2022-12-14  1:23     ` Jakub Kicinski
2022-12-14  8:16       ` 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='CAMZ6Rq+w3ZG5Y=6m+dFL_p3WLUFUkLKarj253nWu9q3+-GOH6Q@mail.gmail.com' \
    --to=mailhol.vincent@wanadoo.fr \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).