From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: kvm@vger.kernel.org, David Airlie <airlied@linux.ie>,
Tom Rix <trix@redhat.com>,
linux-fpga@vger.kernel.org, dri-devel@lists.freedesktop.org,
Harry Wei <harryxiyou@gmail.com>, Will Deacon <will@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
amd-gfx@lists.freedesktop.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
linux-media@vger.kernel.org, Chao Yu <chao@kernel.org>,
Moritz Fischer <mdf@kernel.org>, Jaegeuk Kim <jaegeuk@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Felipe Balbi <balbi@kernel.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
Daniel Vetter <daniel@ffwll.ch>, Wu Hao <hao.wu@intel.com>
Subject: [PATCH 00/10] Fix documentation warnings at linux-next
Date: Thu, 14 Jan 2021 08:53:35 +0100 [thread overview]
Message-ID: <cover.1610610444.git.mchehab+huawei@kernel.org> (raw)
This series fixes the documentation warnings found at next-20210114.
Most of the changes here are trivial.
While those patches could be merged via the docs tree during
the next merge window, It sounds better to have those patches
merged directly via each maintainer's tree, where the new
warnings were introduced.
Regards,
Mauro
Mauro Carvalho Chehab (10):
doc/zh_CN: fix Sphinx errors
ABI: sysfs-fs-f2fs: fix a table identation
KVM: x86: hyper-v: add a blank line to remove building warnings
ABI: sysfs-firmware-sgi_uv
docs: fpga: dfl.rst: Fix a couple building issues
drm: amd: amdgpu_dm.h: fix a wrong kernel-doc markup
dwc3: document gadget_max_speed
doc: zh_CN/mips: fix doc cross-references
media: v4l2-subdev.rst: fix a missing whitespace
seqlock: kernel-doc: fix a prototype
Documentation/ABI/testing/sysfs-firmware-sgi_uv | 1 +
Documentation/ABI/testing/sysfs-fs-f2fs | 3 ++-
Documentation/driver-api/media/v4l2-subdev.rst | 2 +-
Documentation/fpga/dfl.rst | 4 ++--
Documentation/translations/zh_CN/mips/booting.rst | 2 +-
Documentation/translations/zh_CN/mips/features.rst | 2 +-
Documentation/translations/zh_CN/mips/index.rst | 2 +-
Documentation/translations/zh_CN/mips/ingenic-tcu.rst | 6 +++---
Documentation/virt/kvm/api.rst | 1 +
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h | 2 +-
drivers/usb/dwc3/core.h | 1 +
include/linux/seqlock.h | 2 +-
12 files changed, 16 insertions(+), 12 deletions(-)
--
2.29.2
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next reply other threads:[~2021-01-14 7:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 7:53 Mauro Carvalho Chehab [this message]
2021-01-14 7:53 ` [PATCH 06/10] drm: amd: amdgpu_dm.h: fix a wrong kernel-doc markup Mauro Carvalho Chehab
2021-01-14 13:50 ` Christian König
2021-01-14 17:40 ` 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.1610610444.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=airlied@linux.ie \
--cc=amd-gfx@lists.freedesktop.org \
--cc=balbi@kernel.org \
--cc=chao@kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hao.wu@intel.com \
--cc=harryxiyou@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mdf@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=trix@redhat.com \
--cc=will@kernel.org \
/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