From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: kbuild-all@lists.01.org
Subject: Re: [driver-core:driver-core-testing 29/33] include/linux/platform_device.h:75:40: error: unknown type name 'irq_handler_t'
Date: Tue, 08 Sep 2020 13:37:54 +0200 [thread overview]
Message-ID: <20200908113754.GA1453813@kroah.com> (raw)
In-Reply-To: <202009080432.5YpVmPhM%lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]
On Tue, Sep 08, 2020 at 04:21:36AM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git driver-core-testing
> head: fa802fde315b87157f6d7c5dfe5d926bdb97d6e4
> commit: 4f4e9ddba1225e2dcdd08ac91f1e82aaca51f2b8 [29/33] drivers: provide devm_platform_request_irq()
> config: h8300-randconfig-r014-20200907 (attached as .config)
> compiler: h8300-linux-gcc (GCC) 9.3.0
> reproduce (this is a W=1 build):
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout 4f4e9ddba1225e2dcdd08ac91f1e82aaca51f2b8
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=h8300
I'm going to drop this patch, and the follow-up patch for this, from my
trees. Maybe the prototype for this function should go in a different
.h file to resolve these types of build issues?
thanks,
greg k-h
next prev parent reply other threads:[~2020-09-08 11:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 20:21 [driver-core:driver-core-testing 29/33] include/linux/platform_device.h:75:40: error: unknown type name 'irq_handler_t' kernel test robot
2020-09-08 11:37 ` Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-07 20:25 kernel test robot
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=20200908113754.GA1453813@kroah.com \
--to=gregkh@linuxfoundation.org \
--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.