All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Cercueil <paul@crapouillou.net>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-pwm@vger.kernel.org,
	Thierry Reding <thierry.reding@gmail.com>
Subject: Re: [pwm:for-next 13/37] ERROR: "jz4740_timer_base" [drivers/pwm/pwm-jz4740.ko] undefined!
Date: Wed, 26 Jun 2019 02:52:39 +0200	[thread overview]
Message-ID: <1561510359.10069.3@crapouillou.net> (raw)
In-Reply-To: <201906260804.9UofywY8%lkp@intel.com>



Le mer. 26 juin 2019 à 2:47, kbuild test robot <lkp@intel.com> a 
écrit :
> tree:   
> https://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm.git 
> for-next
> head:   cb8338e4fe3a8278cee91f666d2155a0ce1dd82f
> commit: e9bd35ff751fac8755fe3480bec1f470383f4522 [13/37] pwm: jz4740: 
> Drop dependency on MACH_INGENIC
> config: mips-allmodconfig (attached as .config)
> compiler: mips-linux-gcc (GCC) 7.4.0
> reproduce:
>         wget 
> https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross 
> -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         git checkout e9bd35ff751fac8755fe3480bec1f470383f4522
>         # save the attached .config to linux build tree
>         GCC_VERSION=7.4.0 make.cross ARCH=mips
> 
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
> 
> All errors (new ones prefixed by >>):
> 
>  ERROR: "jz4740_timer_base" [drivers/pwm/pwm-jz4740.ko] undefined!

Looks like this patch was a bit premature...
I think you can drop it...

> ---
> 0-DAY kernel test infrastructure                Open Source 
> Technology Center
> https://lists.01.org/pipermail/kbuild-all                   Intel 
> Corporation


  reply	other threads:[~2019-06-26  0:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-26  0:47 [pwm:for-next 13/37] ERROR: "jz4740_timer_base" [drivers/pwm/pwm-jz4740.ko] undefined! kbuild test robot
2019-06-26  0:52 ` Paul Cercueil [this message]
2019-06-26  9:44   ` Thierry Reding

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=1561510359.10069.3@crapouillou.net \
    --to=paul@crapouillou.net \
    --cc=kbuild-all@01.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=thierry.reding@gmail.com \
    /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.