Re: [PATCH v4 00/27]Fix several bad kernel-doc markups

[PATCH v4 00/27]Fix several bad kernel-doc markups · Mauro Carvalho Chehab <mchehab+huawei@kernel.org> · 2020-11-16
[PATCH v4 03/27] net: core: fix some kernel-doc markups · Mauro Carvalho Chehab <mchehab+huawei@kernel.org> · 2020-11-16
[PATCH v4 01/27] net: phy: fix kernel-doc markups · Mauro Carvalho Chehab <mchehab+huawei@kernel.org> · 2020-11-16
[PATCH v4 02/27] net: datagram: fix some kernel-doc markups · Mauro Carvalho Chehab <mchehab+huawei@kernel.org> · 2020-11-16
Re: [PATCH v4 02/27] net: datagram: fix some kernel-doc markups · Kirill Tkhai <hidden> · 2020-11-16
Re: [PATCH v4 00/27]Fix several bad kernel-doc markups · Jakub Kicinski <kuba@kernel.org> · 2020-11-17

From: Jakub Kicinski <kuba@kernel.org>
Date: 2020-11-17 22:19:31
Also in: dri-devel, intel-gfx, linux-doc, linux-ext4, linux-fbdev, linux-fsdevel, linux-kselftest, linux-mm, linux-nfs, linux-rdma, linux-s390, lkml, target-devel

On Mon, 16 Nov 2020 11:17:56 +0100 Mauro Carvalho Chehab wrote:

Kernel-doc has always be limited to a probably bad documented
rule:

The kernel-doc markups should appear *imediatelly before* the
function or data structure that it documents.

Applied 1-3 to net-next, thanks!

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help