public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: [stffrdhrn:or1k-virt 1/4] drivers/parport/parport_pc.c:68:10: fatal error: asm/parport.h: No such file or directory
Date: Wed, 15 Jun 2022 16:29:51 +0900	[thread overview]
Message-ID: <YqmKb4thAtT6za5A@antec> (raw)
In-Reply-To: <202206151530.3eDDbhQ1-lkp@intel.com>

On Wed, Jun 15, 2022 at 03:08:55PM +0800, kernel test robot wrote:
> tree:   https://github.com/stffrdhrn/linux.git or1k-virt
> head:   a0ea15d897c0baa5a4dc8f4ec3c8839527c43e89
> commit: a65c4ddd8782b2255f4387fd1273b96dacc7c8a6 [1/4] openrisc: Add pci bus support
> config: openrisc-allmodconfig (https://download.01.org/0day-ci/archive/20220615/202206151530.3eDDbhQ1-lkp@intel.com/config)
> compiler: or1k-linux-gcc (GCC) 11.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
>         # https://github.com/stffrdhrn/linux/commit/a65c4ddd8782b2255f4387fd1273b96dacc7c8a6
>         git remote add stffrdhrn https://github.com/stffrdhrn/linux.git
>         git fetch --no-tags stffrdhrn or1k-virt
>         git checkout a65c4ddd8782b2255f4387fd1273b96dacc7c8a6
>         # save the config file
>         mkdir build_dir && cp config build_dir/.config
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=openrisc SHELL=/bin/bash drivers/parport/
> 
> If you fix the issue, kindly add following tag where applicable
> Reported-by: kernel test robot <lkp@intel.com>
> 
> All errors (new ones prefixed by >>):
> 
> >> drivers/parport/parport_pc.c:68:10: fatal error: asm/parport.h: No such file or directory
>       68 | #include <asm/parport.h>
>          |          ^~~~~~~~~~~~~~~
>    compilation terminated.

Interesting, since commit 66bcd06099bb ("parport_pc: Also enable driver for PCI
systems") all PCI systems also need to support parport.  I have added a generic
include to provide asm/parport.h now to this branch.

Thanks,

-Stafford

> 
> vim +68 drivers/parport/parport_pc.c
> 
> ^1da177e4c3f41 Linus Torvalds 2005-04-16  64  
> ^1da177e4c3f41 Linus Torvalds 2005-04-16  65  #include <linux/parport.h>
> ^1da177e4c3f41 Linus Torvalds 2005-04-16  66  #include <linux/parport_pc.h>
> ^1da177e4c3f41 Linus Torvalds 2005-04-16  67  #include <linux/via.h>
> ^1da177e4c3f41 Linus Torvalds 2005-04-16 @68  #include <asm/parport.h>
> ^1da177e4c3f41 Linus Torvalds 2005-04-16  69  
> 
> :::::: The code at line 68 was first introduced by commit
> :::::: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Linux-2.6.12-rc2
> 
> :::::: TO: Linus Torvalds <torvalds@ppc970.osdl.org>
> :::::: CC: Linus Torvalds <torvalds@ppc970.osdl.org>
> 
> -- 
> 0-DAY CI Kernel Test Service
> https://01.org/lkp

      reply	other threads:[~2022-06-15  7:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-15  7:08 [stffrdhrn:or1k-virt 1/4] drivers/parport/parport_pc.c:68:10: fatal error: asm/parport.h: No such file or directory kernel test robot
2022-06-15  7:29 ` Stafford Horne [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=YqmKb4thAtT6za5A@antec \
    --to=shorne@gmail.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox