From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: "Luben Tuikov" <luben.tuikov@amd.com>,
kunit-dev@googlegroups.com, "David Airlie" <airlied@linux.ie>,
"Brendan Higgins" <brendanhiggins@google.com>,
dri-devel@lists.freedesktop.org, target-devel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
"Max Gurtovoy" <maxg@mellanox.com>,
"Will Deacon" <will@kernel.org>,
"Ard Biesheuvel" <ardb@kernel.org>,
"Bart Van Assche" <bvanassche@acm.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>,
"Bernard Zhao" <bernard@vivo.com>,
amd-gfx@lists.freedesktop.org, "Ingo Molnar" <mingo@kernel.org>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"Doug Ledford" <dledford@redhat.com>,
"Colton Lewis" <colton.w.lewis@protonmail.com>,
"Ben Skeggs" <bskeggs@redhat.com>,
"Johannes Thumshirn" <jthumshirn@suse.de>,
"Dave Airlie" <airlied@redhat.com>,
"Iurii Zaikin" <yzaikin@google.com>,
"Dennis Li" <Dennis.Li@amd.com>,
linux-rdma@vger.kernel.org,
"Yamin Friedman" <yaminf@mellanox.com>,
"Andrey Grodzovsky" <andrey.grodzovsky@amd.com>,
"Kees Cook" <keescook@chromium.org>,
"Jann Horn" <jannh@google.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Josef Bacik" <josef@toxicpanda.com>,
"Christophe JAILLET" <christophe.jaillet@wanadoo.fr>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"David Sterba" <dsterba@suse.com>,
"Evan Quan" <evan.quan@amd.com>, "Ingo Molnar" <mingo@redhat.com>,
"Sagi Grimberg" <sagi@grimberg.me>,
"Stephen Boyd" <sboyd@kernel.org>,
linux-kernel@vger.kernel.org,
"Nikolay Borisov" <nborisov@suse.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Goldwyn Rodrigues" <rgoldwyn@suse.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Alan Maguire" <alan.maguire@oracle.com>,
"Christian König" <christian.koenig@amd.com>,
"Hawking Zhang" <Hawking.Zhang@amd.com>
Subject: [PATCH v3 0/6] Documentation build fixes against upstream
Date: Wed, 21 Oct 2020 14:17:21 +0200 [thread overview]
Message-ID: <cover.1603282193.git.mchehab+huawei@kernel.org> (raw)
As we're close to the end of the merge window for Kernel 5.10,
this series contain the patches from the past two documentation
fix series I sent during the merge window and that required more
work.
It is based on the top of upstream. The full series with the patches
that either didn't generate any reply or have been acked is on
this branch:
https://git.linuxtv.org/mchehab/experimental.git/log/?h=docs_for_v5.10
There are a couple of warnings that aren't addressed here, because
they don't show at linux-next. I'm keeping a second patch series
against next-20201021 fixing additional warnings caused by patches
pending merges.
I'll be posting those in separate.
Regards,
Mauro
Mauro Carvalho Chehab (6):
drm: amdgpu: kernel-doc: update some adev parameters
docs: lockdep-design: fix some warning issues
locking/refcount: move kernel-doc markups to the proper place
IB/srpt: docs: add a description for cq_size member
kunit: test: fix remaining kernel-doc warnings
docs: fs: api-summary.rst: get rid of kernel-doc include
Documentation/filesystems/api-summary.rst | 3 -
Documentation/locking/lockdep-design.rst | 51 +++---
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 28 ++--
drivers/gpu/drm/amd/amdgpu/amdgpu_gtt_mgr.c | 6 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c | 7 +-
drivers/infiniband/ulp/srpt/ib_srpt.h | 1 +
include/kunit/test.h | 16 +-
include/linux/refcount.h | 158 +++++++++----------
8 files changed, 139 insertions(+), 131 deletions(-)
--
2.26.2
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next reply other threads:[~2020-10-21 12:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 12:17 Mauro Carvalho Chehab [this message]
2020-10-21 12:17 ` [PATCH v3 1/6] drm: amdgpu: kernel-doc: update some adev parameters Mauro Carvalho Chehab
2020-10-21 18:37 ` Alex Deucher
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.1603282193.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=Dennis.Li@amd.com \
--cc=Hawking.Zhang@amd.com \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=alan.maguire@oracle.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andrey.grodzovsky@amd.com \
--cc=ardb@kernel.org \
--cc=bernard@vivo.com \
--cc=boqun.feng@gmail.com \
--cc=brendanhiggins@google.com \
--cc=bskeggs@redhat.com \
--cc=bvanassche@acm.org \
--cc=christian.koenig@amd.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=colton.w.lewis@protonmail.com \
--cc=corbet@lwn.net \
--cc=daniel@ffwll.ch \
--cc=dledford@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=dsterba@suse.com \
--cc=evan.quan@amd.com \
--cc=jannh@google.com \
--cc=jgg@ziepe.ca \
--cc=josef@toxicpanda.com \
--cc=jthumshirn@suse.de \
--cc=keescook@chromium.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=luben.tuikov@amd.com \
--cc=maxg@mellanox.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=nborisov@suse.com \
--cc=peterz@infradead.org \
--cc=rgoldwyn@suse.com \
--cc=sagi@grimberg.me \
--cc=sboyd@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=target-devel@vger.kernel.org \
--cc=will@kernel.org \
--cc=yaminf@mellanox.com \
--cc=yzaikin@google.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