linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Richard Weinberger <richard@nod.at>, linux-kernel@vger.kernel.org
Cc: linux-iio@vger.kernel.org,
	Maxime Ripard <maxime.ripard@free-electrons.com>
Subject: Re: [PATCH 5/8] nvmem: Fix io memory dependencies
Date: Wed, 30 Mar 2016 09:50:39 +0100	[thread overview]
Message-ID: <56FB935F.4000404@linaro.org> (raw)
In-Reply-To: <1458945655-5027-5-git-send-email-richard@nod.at>

Thanks for the patch,

But there is already a same patch [1] submitted few days back.
I will pick that one.


Thanks,
srini

[1] http://lkml.iu.edu/hypermail/linux/kernel/1603.0/03538.html

On 25/03/16 22:40, Richard Weinberger wrote:
> Not all archs have io memory.
>
> Fixes the following build error:
> ERROR: "devm_ioremap_resource" [drivers/nvmem/nvmem_mtk-efuse.ko] undefined!
> ERROR: "devm_ioremap_resource" [drivers/nvmem/nvmem_lpc18xx_eeprom.ko] undefined!
>
> Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
> Cc: Maxime Ripard <maxime.ripard@free-electrons.com>
> Signed-off-by: Richard Weinberger <richard@nod.at>
> ---
>   drivers/nvmem/Kconfig | 2 ++
>   1 file changed, 2 insertions(+)
>
> diff --git a/drivers/nvmem/Kconfig b/drivers/nvmem/Kconfig
> index ca52952..3766da3 100644
> --- a/drivers/nvmem/Kconfig
> +++ b/drivers/nvmem/Kconfig
> @@ -27,6 +27,7 @@ config NVMEM_IMX_OCOTP
>
>   config NVMEM_LPC18XX_EEPROM
>   	tristate "NXP LPC18XX EEPROM Memory Support"
> +	depends on HAS_IOMEM
>   	depends on ARCH_LPC18XX || COMPILE_TEST
>   	help
>   	  Say Y here to include support for NXP LPC18xx EEPROM memory found in
> @@ -48,6 +49,7 @@ config NVMEM_MXS_OCOTP
>
>   config MTK_EFUSE
>   	tristate "Mediatek SoCs EFUSE support"
> +	depends on HAS_IOMEM
>   	depends on ARCH_MEDIATEK || COMPILE_TEST
>   	select REGMAP_MMIO
>   	help
>

  reply	other threads:[~2016-03-30  8:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-25 22:40 [PATCH 1/8] phy: Fix phy-hi6220-usb dependencies Richard Weinberger
2016-03-25 22:40 ` [PATCH 2/8] mailbox: Fix rockchip dependencies Richard Weinberger
2016-03-25 22:40 ` [PATCH 3/8] phy: Fix phy-omap-control dependencies Richard Weinberger
2016-03-25 22:40 ` [PATCH 4/8] phy: Fix phy-bcm-cygnus-pcie dependencies Richard Weinberger
2016-03-25 22:40 ` [PATCH 5/8] nvmem: Fix io memory dependencies Richard Weinberger
2016-03-30  8:50   ` Srinivas Kandagatla [this message]
2016-03-25 22:40 ` [PATCH 6/8] iio: adc: Fix at91-sama5d2_adc dependencies Richard Weinberger
2016-03-28  8:44   ` Jonathan Cameron
2016-03-25 22:40 ` [PATCH 7/8] fpga: Fix zynq-fpga dependencies Richard Weinberger
2016-03-25 22:40 ` [PATCH 8/8] iio: imu: Fix inv_mpu6050 dependencies Richard Weinberger
2016-03-28  9:03   ` Jonathan Cameron
2016-03-26  9:05 ` [PATCH 1/8] phy: Fix phy-hi6220-usb dependencies Geert Uytterhoeven
2016-03-26  9:27   ` Richard Weinberger
2016-03-30  4:15 ` Krzysztof Kozlowski

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=56FB935F.4000404@linaro.org \
    --to=srinivas.kandagatla@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=richard@nod.at \
    /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).