[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221213172351.4d251315@kernel.org>
Date: Tue, 13 Dec 2022 17:23:51 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Marc Kleine-Budde <mkl@...gutronix.de>
Cc: Vincent Mailhol <mailhol.vincent@...adoo.fr>,
Stephen Rothwell <sfr@...b.auug.org.au>,
David Miller <davem@...emloft.net>,
Networking <netdev@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: [PATCH] Documentation: devlink: add missing toc entry for
etas_es58x devlink doc
On Tue, 13 Dec 2022 14:39:54 +0100 Marc Kleine-Budde 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@...adoo.fr>
>
> Added to linux-can-next + added Reported-bys.
To -next or not to -next, that is the question..
FWIW the code is now in Linus's tree, but IDK how you forward your
trees. We could also take this directly given the file being changed,
but up to you.
Powered by blists - more mailing lists