From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Alexander Potapenko <glider@google.com>,
Alexei Starovoitov <ast@kernel.org>,
Andreas Gruenbacher <agruenba@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Andrii Nakryiko <andriin@fb.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Dmitry Vyukov <dvyukov@google.com>,
Guoqing Jiang <guoqing.jiang@cloud.ionos.com>,
Jens Axboe <axboe@kernel.dk>,
Johannes Weiner <hannes@cmpxchg.org>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@chromium.org>, Martin KaFai Lau <kafai@fb.com>,
Song Liu <songliubraving@fb.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
William Kucharski <william.kucharski@oracle.com>,
Yang Shi <yang.shi@linux.alibaba.com>, Yonghong Song <yhs@fb.com>,
bpf@vger.kernel.org, kasan-dev@googlegroups.com,
netdev@vger.kernel.org
Subject: [PATCH 0/3] Additional doc warning fixes for issues at next-20200915
Date: Thu, 17 Sep 2020 10:04:24 +0200 [thread overview]
Message-ID: <cover.1600328701.git.mchehab+huawei@kernel.org> (raw)
There are a couple of new warnings introduced at linux-next.
This small patch series address them.
The complete series addressing (almost) all doc warnings is at:
https://git.linuxtv.org/mchehab/experimental.git/log/?h=doc-fixes
I'll keep rebasing such tree until we get rid of all doc warnings upstream,
hopefully in time for Kernel 5.10.
Mauro Carvalho Chehab (3):
docs: kasan.rst: add two missing blank lines
mm: pagemap.h: fix two kernel-doc markups
docs: bpf: ringbuf.rst: fix a broken cross-reference
Documentation/bpf/ringbuf.rst | 2 +-
Documentation/dev-tools/kasan.rst | 2 ++
include/linux/pagemap.h | 8 ++++----
3 files changed, 7 insertions(+), 5 deletions(-)
--
2.26.2
next reply other threads:[~2020-09-17 8:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 8:04 Mauro Carvalho Chehab [this message]
2020-09-17 8:04 ` [PATCH 1/3] docs: kasan.rst: add two missing blank lines Mauro Carvalho Chehab
2020-09-18 11:44 ` Andrey Konovalov
2020-09-17 8:04 ` [PATCH 2/3] mm: pagemap.h: fix two kernel-doc markups Mauro Carvalho Chehab
2020-09-17 8:04 ` [PATCH 3/3] docs: bpf: ringbuf.rst: fix a broken cross-reference Mauro Carvalho Chehab
2020-09-17 14:57 ` Alexei Starovoitov
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=cover.1600328701.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=agruenba@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andriin@fb.com \
--cc=aryabinin@virtuozzo.com \
--cc=ast@kernel.org \
--cc=axboe@kernel.dk \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=guoqing.jiang@cloud.ionos.com \
--cc=hannes@cmpxchg.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kasan-dev@googlegroups.com \
--cc=kpsingh@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=songliubraving@fb.com \
--cc=william.kucharski@oracle.com \
--cc=willy@infradead.org \
--cc=yang.shi@linux.alibaba.com \
--cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).