From: Lee Jones <lee.jones@linaro.org>
To: lee.jones@linaro.org
Cc: linux-kernel@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Anton Vorontsov <anton@enomsg.org>,
benh@kernel.crashing.org, Colin Cross <ccross@android.com>,
"David S. Miller" <davem@davemloft.net>,
devicetree@vger.kernel.org, Frank Rowand <frowand.list@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Josh Cartwright <joshc@codeaurora.org>,
Kees Cook <keescook@chromium.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
netdev@vger.kernel.org,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
Rob Herring <robh+dt@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Tony Luck <tony.luck@intel.com>
Subject: [PATCH 00/10] Rid W=1 warnings from OF
Date: Fri, 12 Mar 2021 11:07:48 +0000 [thread overview]
Message-ID: <20210312110758.2220959-1-lee.jones@linaro.org> (raw)
This set is part of a larger effort attempting to clean-up W=1
kernel builds, which are currently overwhelmingly riddled with
niggly little warnings.
Lee Jones (10):
of: device: Fix function name in header and demote kernel-doc abuse
of: dynamic: Fix incorrect parameter name and demote kernel-doc abuse
of: platform: Demote kernel-doc abuse
of: base: Fix some formatting issues and demote non-conformant
kernel-doc headers
of: property: Provide missing member description and remove excess
param
of: address: Demote non-conformant kernel-doc header
of: fdt: Demote kernel-doc abuses
of: of_net: Demote non-conforming kernel-doc header
of: overlay: Fix function name disparity
of: of_reserved_mem: Demote kernel-doc abuses
drivers/of/address.c | 2 +-
drivers/of/base.c | 16 ++++++++--------
drivers/of/device.c | 6 +++---
drivers/of/dynamic.c | 6 +++---
drivers/of/fdt.c | 19 ++++++++++---------
drivers/of/of_net.c | 2 +-
drivers/of/of_reserved_mem.c | 6 +++---
drivers/of/overlay.c | 2 +-
drivers/of/platform.c | 2 +-
drivers/of/property.c | 2 +-
10 files changed, 32 insertions(+), 31 deletions(-)
Cc: Andrew Lunn <andrew@lunn.ch>
Cc: Anton Vorontsov <anton@enomsg.org>
Cc: benh@kernel.crashing.org
Cc: Colin Cross <ccross@android.com>
Cc: "David S. Miller" <davem@davemloft.net>
Cc: devicetree@vger.kernel.org
Cc: Frank Rowand <frowand.list@gmail.com>
Cc: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Josh Cartwright <joshc@codeaurora.org>
Cc: Kees Cook <keescook@chromium.org>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: netdev@vger.kernel.org
Cc: Pantelis Antoniou <pantelis.antoniou@konsulko.com>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: Russell King <linux@armlinux.org.uk>
Cc: Tony Luck <tony.luck@intel.com>
--
2.27.0
next reply other threads:[~2021-03-12 11:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 11:07 Lee Jones [this message]
2021-03-12 11:07 ` [PATCH 08/10] of: of_net: Demote non-conforming kernel-doc header Lee Jones
2021-03-12 14:05 ` Andrew Lunn
2021-03-12 15:18 ` Lee Jones
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=20210312110758.2220959-1-lee.jones@linaro.org \
--to=lee.jones@linaro.org \
--cc=andrew@lunn.ch \
--cc=anton@enomsg.org \
--cc=benh@kernel.crashing.org \
--cc=ccross@android.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=joshc@codeaurora.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=netdev@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=robh+dt@kernel.org \
--cc=tony.luck@intel.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).