All of lore.kernel.org
 help / color / mirror / Atom feed
From: LABBE Corentin <clabbe@baylibre.com>
To: kbuild-all@lists.01.org
Subject: Re: [linux-next:master 8194/11253] ERROR: modpost: "devm_platform_ioremap_resource" [drivers/crypto/gemini/sl3516-ce.ko] undefined!
Date: Fri, 18 Jun 2021 22:40:29 +0200	[thread overview]
Message-ID: <YM0EvUisnu6DpLn/@Red> (raw)
In-Reply-To: <202106190336.QwTPDfIF-lkp@intel.com>

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

Le Sat, Jun 19, 2021 at 03:23:39AM +0800, kernel test robot a écrit :
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head:   e71e3a48a7e89fa71fb70bf4602367528864d2ff
> commit: 46c5338db7bd45b2cf99570560f00389d60fd6b4 [8194/11253] crypto: sl3516 - Add sl3516 crypto engine
> config: um-allmodconfig (attached as .config)
> compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
> reproduce (this is a W=1 build):
>         # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=46c5338db7bd45b2cf99570560f00389d60fd6b4
>         git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>         git fetch --no-tags linux-next master
>         git checkout 46c5338db7bd45b2cf99570560f00389d60fd6b4
>         # save the attached .config to linux build tree
>         make W=1 ARCH=um 
> 
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
> 
> All errors (new ones prefixed by >>, old ones prefixed by <<):
> 
> >> ERROR: modpost: "devm_platform_ioremap_resource" [drivers/crypto/gemini/sl3516-ce.ko] undefined!

Thanks for the report.

I will send the fix soon.
Regards

WARNING: multiple messages have this Message-ID (diff)
From: LABBE Corentin <clabbe@baylibre.com>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [linux-next:master 8194/11253] ERROR: modpost: "devm_platform_ioremap_resource" [drivers/crypto/gemini/sl3516-ce.ko] undefined!
Date: Fri, 18 Jun 2021 22:40:29 +0200	[thread overview]
Message-ID: <YM0EvUisnu6DpLn/@Red> (raw)
In-Reply-To: <202106190336.QwTPDfIF-lkp@intel.com>

Le Sat, Jun 19, 2021 at 03:23:39AM +0800, kernel test robot a écrit :
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head:   e71e3a48a7e89fa71fb70bf4602367528864d2ff
> commit: 46c5338db7bd45b2cf99570560f00389d60fd6b4 [8194/11253] crypto: sl3516 - Add sl3516 crypto engine
> config: um-allmodconfig (attached as .config)
> compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
> reproduce (this is a W=1 build):
>         # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=46c5338db7bd45b2cf99570560f00389d60fd6b4
>         git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>         git fetch --no-tags linux-next master
>         git checkout 46c5338db7bd45b2cf99570560f00389d60fd6b4
>         # save the attached .config to linux build tree
>         make W=1 ARCH=um 
> 
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
> 
> All errors (new ones prefixed by >>, old ones prefixed by <<):
> 
> >> ERROR: modpost: "devm_platform_ioremap_resource" [drivers/crypto/gemini/sl3516-ce.ko] undefined!

Thanks for the report.

I will send the fix soon.
Regards


  reply	other threads:[~2021-06-18 20:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-18 19:23 [linux-next:master 8194/11253] ERROR: modpost: "devm_platform_ioremap_resource" [drivers/crypto/gemini/sl3516-ce.ko] undefined! kernel test robot
2021-06-18 19:23 ` kernel test robot
2021-06-18 20:40 ` LABBE Corentin [this message]
2021-06-18 20:40   ` LABBE Corentin

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=YM0EvUisnu6DpLn/@Red \
    --to=clabbe@baylibre.com \
    --cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.