From: YueHaibing <yuehaibing@huawei.com>
To: <TheSven73@gmail.com>, <gregkh@linuxfoundation.org>
Cc: <linux-kernel@vger.kernel.org>, <devel@driverdev.osuosl.org>
Subject: Re: [PATCH v2 -next] staging: fieldbus: Fix build error without CONFIG_REGMAP_MMIO
Date: Tue, 28 May 2019 22:36:43 +0800 [thread overview]
Message-ID: <428cde8a-00cd-9023-9f09-deec4834507d@huawei.com> (raw)
In-Reply-To: <20190528142912.13224-1-yuehaibing@huawei.com>
Sorry, this is broken, Pls igore this.
On 2019/5/28 22:29, YueHaibing wrote:
> Fix gcc build error while CONFIG_REGMAP_MMIO is not set
>
> drivers/staging/fieldbus/anybuss/arcx-anybus.o: In function `controller_probe':
> arcx-anybus.c: undefined reference to `__devm_regmap_init_mmio_clk'
>
> Select REGMAP_MMIO to fix it.
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Fixes: 2411a336c8ce ("staging: fieldbus: arcx-anybus: change custom -> mmio regmap")
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> ---
> v2: fix patch style warning
> ---
> drivers/staging/fieldbus/anybuss/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/staging/fieldbus/anybuss/Kconfig b/drivers/staging/fieldbus/anybuss/Kconfig
> index 8bc3d9a..635a0a7 100644
> --- a/drivers/staging/fieldbus/anybuss/Kconfig
> +++ b/drivers/staging/fieldbus/anybuss/Kconfig
> @@ -14,6 +14,7 @@ if HMS_ANYBUSS_BUS
> config ARCX_ANYBUS_CONTROLLER
> tristate "Arcx Anybus-S Controller"
> depends on OF && GPIOLIB && HAS_IOMEM && REGULATOR
> + select REGMAP_MMIO
> help
> Select this to get support for the Arcx Anybus controller.
> It connects to the SoC via a parallel memory bus, and
>
prev parent reply other threads:[~2019-05-28 14:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 13:32 [PATCH -next] staging: fieldbus: Fix build error without CONFIG_REGMAP_MMIO YueHaibing
2019-05-28 13:41 ` Sven Van Asbroeck
2019-05-28 14:10 ` YueHaibing
2019-05-28 14:29 ` [PATCH v2 " YueHaibing
2019-05-28 14:35 ` Sven Van Asbroeck
2019-05-28 15:41 ` YueHaibing
2019-05-28 15:59 ` Greg KH
2019-05-28 17:31 ` Sven Van Asbroeck
2019-06-10 12:51 ` Sven Van Asbroeck
2019-06-10 14:09 ` Greg KH
2019-05-28 14:36 ` YueHaibing [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=428cde8a-00cd-9023-9f09-deec4834507d@huawei.com \
--to=yuehaibing@huawei.com \
--cc=TheSven73@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).