mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>, srini@kernel.org
Cc: linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] nvmem: rmem: fix undefined reference to memremap
Date: Mon, 15 Mar 2021 11:46:41 +0100	[thread overview]
Message-ID: <dd4b1b389faf7b0219e1dccf48e17126887b3c70.camel@suse.de> (raw)
In-Reply-To: <20210315104457.18140-1-srinivas.kandagatla@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]

On Mon, 2021-03-15 at 10:44 +0000, Srinivas Kandagatla wrote:
> Fix below error reporte by kernel test robot
> rmem.c:(.text+0x14e): undefined reference to memremap
> s390x-linux-gnu-ld: rmem.c:(.text+0x1b6): undefined reference to memunmap
> 
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
> ---

Reviewed-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>

Thanks!

>  drivers/nvmem/Kconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/nvmem/Kconfig b/drivers/nvmem/Kconfig
> index 642ddc699fd1..dd2019006838 100644
> --- a/drivers/nvmem/Kconfig
> +++ b/drivers/nvmem/Kconfig
> @@ -272,6 +272,7 @@ config SPRD_EFUSE
>  
> 
>  config NVMEM_RMEM
>  	tristate "Reserved Memory Based Driver Support"
> +	depends on HAS_IOMEM
>  	help
>  	  This driver maps reserved memory into an nvmem device. It might be
>  	  useful to expose information left by firmware in memory.



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2021-03-15 10:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-15 10:44 Srinivas Kandagatla
2021-03-15 10:46 ` Nicolas Saenz Julienne [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=dd4b1b389faf7b0219e1dccf48e17126887b3c70.camel@suse.de \
    --to=nsaenzjulienne@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=srini@kernel.org \
    --cc=srinivas.kandagatla@linaro.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

all inboxes | Powered by JetHome®