From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: <linux-kernel@vger.kernel.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
<patches@opensource.cirrus.com>
Subject: Re: [PATCH 1/7] mfd: wm831x-core: Fix incorrect function name wm831x_reg_unlock()
Date: Fri, 21 May 2021 09:02:26 +0000 [thread overview]
Message-ID: <20210521090226.GJ64205@ediswmail.ad.cirrus.com> (raw)
In-Reply-To: <20210520120820.3465562-2-lee.jones@linaro.org>
On Thu, May 20, 2021 at 01:08:14PM +0100, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/mfd/wm831x-core.c:121: warning: expecting prototype for wm831x_reg_unlock(). Prototype was for wm831x_reg_lock() instead
>
> Cc: Lee Jones <lee.jones@linaro.org>
> Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>
> Cc: patches@opensource.cirrus.com
> Signed-off-by: Lee Jones <lee.jones@linaro.org>
> ---
Acked-by: Charles Keepax <ckeepax@opensource.cirrus.com>
Thanks,
Charles
next prev parent reply other threads:[~2021-05-21 9:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 12:08 [PATCH 0/7] Rid W=1 warnings from MFD Lee Jones
2021-05-20 12:08 ` [PATCH 1/7] mfd: wm831x-core: Fix incorrect function name wm831x_reg_unlock() Lee Jones
2021-05-21 9:02 ` Charles Keepax [this message]
2021-05-20 12:08 ` [PATCH 2/7] mfd: twl-core: Fix incorrect function name twl_regcache_bypass() Lee Jones
2021-05-20 12:08 ` [PATCH 3/7] mfd: db8500-prcmu: Fix multiple incorrectly documented function names Lee Jones
2021-05-20 12:08 ` [PATCH 4/7] mfd: omap-usb-host: File headers are not good candidates for kernel-doc Lee Jones
2021-05-20 12:08 ` [PATCH 5/7] mfd: omap-usb-tll: " Lee Jones
2021-05-20 12:08 ` [PATCH 6/7] mfd: si476x-cmd: Fix a bunch of incorrectly documented function names Lee Jones
2021-05-20 12:08 ` [PATCH 7/7] mfd: si476x-i2c: Fix " 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=20210521090226.GJ64205@ediswmail.ad.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.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 read-only IMAP folder(s) and NNTP newsgroup(s).