From: Vinod Koul <vkoul@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: Changhuang Liang <changhuang.liang@starfivetech.com>,
oe-kbuild-all@lists.linux.dev, Kishon <kishon@ti.com>,
Minda Chen <minda.chen@starfivetech.com>
Subject: Re: [phy:next 50/55] ERROR: modpost: "devm_platform_ioremap_resource" [drivers/phy/starfive/phy-jh7110-dphy-rx.ko] undefined!
Date: Tue, 25 Jul 2023 11:52:53 +0530 [thread overview]
Message-ID: <ZL9qPZkF+m6ZrnAk@matsya> (raw)
In-Reply-To: <202307250509.oeudxG28-lkp@intel.com>
On 25-07-23, 05:51, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy.git next
> head: 486392f44dd96aeb34bbbc1b119bc5d332f1164f
> commit: f8aa660841bca12aed51c967ed9bdaf1d97996ed [50/55] phy: starfive: Add mipi dphy rx support
> config: s390-allmodconfig (https://download.01.org/0day-ci/archive/20230725/202307250509.oeudxG28-lkp@intel.com/config)
> compiler: s390-linux-gcc (GCC) 12.3.0
> reproduce: (https://download.01.org/0day-ci/archive/20230725/202307250509.oeudxG28-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202307250509.oeudxG28-lkp@intel.com/
This would be resolved by HAS_IOMEM dependency, sent a patch as well
--
~Vinod
prev parent reply other threads:[~2023-07-25 6:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 21:51 [phy:next 50/55] ERROR: modpost: "devm_platform_ioremap_resource" [drivers/phy/starfive/phy-jh7110-dphy-rx.ko] undefined! kernel test robot
2023-07-25 6:22 ` Vinod Koul [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=ZL9qPZkF+m6ZrnAk@matsya \
--to=vkoul@kernel.org \
--cc=changhuang.liang@starfivetech.com \
--cc=kishon@ti.com \
--cc=lkp@intel.com \
--cc=minda.chen@starfivetech.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.