linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	"Peter Zijlstra (Intel)" <peterz@infradead.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Alex Shi <alex.shi@linux.alibaba.com>,
	Bailu Lin <bailu.lin@vivo.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Harry Wei <harryxiyou@gmail.com>,
	Joel Fernandes <joel@joelfernandes.org>,
	Josh Triplett <josh@joshtriplett.org>,
	Kees Cook <keescook@chromium.org>,
	Lai Jiangshan <jiangshanlai@gmail.com>,
	Luis Chamberlain <mcgrof@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	Scott Branden <scott.branden@broadcom.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Will Deacon <will@kernel.org>,
	rcu@vger.kernel.org
Subject: [PATCH 0/4] linu-next next-20201006 document build fixes
Date: Tue,  6 Oct 2020 15:21:29 +0200	[thread overview]
Message-ID: <cover.1601990386.git.mchehab+huawei@kernel.org> (raw)

This small series fix new warnings introduced on today's linux-next.

Feel free to add the patches on this series at the same tree
as the warning was introduced at the first place.

Thanks!
Mauro


Mauro Carvalho Chehab (4):
  docs: infrastructure.rst: exclude device_link_state from device.h
  docs: zh_CN: amu.rst: fix document title markup
  docs: RCU: Requirements.rst: fix a list block
  firmware_loader: fix a kernel-doc markup

 Documentation/RCU/Design/Requirements/Requirements.rst | 1 +
 Documentation/driver-api/infrastructure.rst            | 1 +
 Documentation/translations/zh_CN/arm64/amu.rst         | 4 ++--
 drivers/base/firmware_loader/fallback.c                | 2 ++
 4 files changed, 6 insertions(+), 2 deletions(-)

-- 
2.26.2



             reply	other threads:[~2020-10-06 13:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-06 13:21 Mauro Carvalho Chehab [this message]
2020-10-06 13:21 ` [PATCH 1/4] docs: infrastructure.rst: exclude device_link_state from device.h Mauro Carvalho Chehab
2020-10-06 13:21 ` [PATCH 2/4] docs: zh_CN: amu.rst: fix document title markup Mauro Carvalho Chehab
2020-10-06 13:21 ` [PATCH 3/4] docs: RCU: Requirements.rst: fix a list block Mauro Carvalho Chehab
2020-10-06 16:36   ` Paul E. McKenney
2020-10-06 13:21 ` [PATCH 4/4] firmware_loader: fix a kernel-doc markup Mauro Carvalho Chehab

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.1601990386.git.mchehab+huawei@kernel.org \
    --to=mchehab+huawei@kernel.org \
    --cc=alex.shi@linux.alibaba.com \
    --cc=bailu.lin@vivo.com \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=harryxiyou@gmail.com \
    --cc=jiangshanlai@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=josh@joshtriplett.org \
    --cc=keescook@chromium.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mcgrof@kernel.org \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rafael@kernel.org \
    --cc=rcu@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=scott.branden@broadcom.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;
as well as URLs for NNTP newsgroup(s).