From: Lee Jones <lee.jones@linaro.org>
To: Anders Roxell <anders.roxell@linaro.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] drivers: mfd: 88pm800: fix warning same module names
Date: Wed, 12 Jun 2019 11:21:21 +0100 [thread overview]
Message-ID: <20190612102121.GI4797@dell> (raw)
In-Reply-To: <20190612081203.1477-1-anders.roxell@linaro.org>
On Wed, 12 Jun 2019, Anders Roxell wrote:
> When building with CONFIG_MFD_88PM800 and CONFIG_REGULATOR_88PM800
> enabled as loadable modules, we see the following warning:
>
> warning: same module names found:
> drivers/regulator/88pm800.ko
> drivers/mfd/88pm800.ko
>
> Rework so the names matches the config fragment.
Please detail what this actually changes.
I.e. what the new modules names will be.
> Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
> ---
> drivers/mfd/Makefile | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mfd/Makefile b/drivers/mfd/Makefile
> index 52b1a90ff515..5e870eef6a20 100644
> --- a/drivers/mfd/Makefile
> +++ b/drivers/mfd/Makefile
> @@ -5,8 +5,11 @@
>
> 88pm860x-objs := 88pm860x-core.o 88pm860x-i2c.o
> obj-$(CONFIG_MFD_88PM860X) += 88pm860x.o
> -obj-$(CONFIG_MFD_88PM800) += 88pm800.o 88pm80x.o
> -obj-$(CONFIG_MFD_88PM805) += 88pm805.o 88pm80x.o
> +obj-$(CONFIG_MFD_88PM800) += mfd-88pm800.o mfd-88pm80x.o
> +mfd-88pm800-objs := 88pm800.o
> +obj-$(CONFIG_MFD_88PM805) += mfd-88pm805.o mfd-88pm80x.o
> +mfd-88pm805-objs := 88pm805.o
> +mfd-88pm80x-objs := 88pm80x.o
> obj-$(CONFIG_MFD_ACT8945A) += act8945a.o
> obj-$(CONFIG_MFD_SM501) += sm501.o
> obj-$(CONFIG_MFD_ASIC3) += asic3.o tmio_core.o
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2019-06-12 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 8:12 [PATCH v2] drivers: mfd: 88pm800: fix warning same module names Anders Roxell
2019-06-12 10:21 ` Lee Jones [this message]
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=20190612102121.GI4797@dell \
--to=lee.jones@linaro.org \
--cc=anders.roxell@linaro.org \
--cc=linux-kernel@vger.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