From: Suman Anna <s-anna@ti.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: <linux-remoteproc@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, Suman Anna <s-anna@ti.com>
Subject: [PATCH 0/2] Minor remoteproc cleanups
Date: Wed, 19 May 2021 13:03:02 -0500 [thread overview]
Message-ID: <20210519180304.23563-1-s-anna@ti.com> (raw)
Hi Bjorn, Mathieu,
The following series is minor document related cleanups. Some
of the warnings look to be very old, and these are not functional
issues, so I am not expecting these to be -stable content, and so
I did not split or add any Fixes: tags.
Patch 1 fixes a warning when building remoteproc core files with W=1,
and Patch 2 fixes all the existing kernel-doc warnings.
Patches are on top of v5.13-rc1.
regards
Suman
Suman Anna (2):
remoteproc: Add kernel-doc comment for is_iomem
remoteproc: Fix various kernel-doc warnings
drivers/remoteproc/remoteproc_core.c | 45 +++++++++++++------
drivers/remoteproc/remoteproc_elf_loader.c | 12 ++++--
drivers/remoteproc/remoteproc_virtio.c | 6 ++-
include/linux/remoteproc.h | 50 ++++++++++++----------
4 files changed, 70 insertions(+), 43 deletions(-)
--
2.30.1
next reply other threads:[~2021-05-19 18:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 18:03 Suman Anna [this message]
2021-05-19 18:03 ` [PATCH 1/2] remoteproc: Add kernel-doc comment for is_iomem Suman Anna
2021-05-25 17:37 ` Mathieu Poirier
2021-05-19 18:03 ` [PATCH 2/2] remoteproc: Fix various kernel-doc warnings Suman Anna
2021-05-25 18:00 ` Mathieu Poirier
2021-05-25 18:07 ` Suman Anna
2021-05-28 3:07 ` Bjorn Andersson
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=20210519180304.23563-1-s-anna@ti.com \
--to=s-anna@ti.com \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.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).