mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Alban Bedel <albeu@free.fr>
Cc: kbuild-all@01.org, linux-gpio@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Linus Walleij <linus.walleij@linaro.org>,
	Alexandre Courbot <gnurou@gmail.com>, Alban Bedel <albeu@free.fr>
Subject: Re: [PATCH 2/3] gpio: ath79: Move to the generic GPIO driver
Date: Fri, 30 Oct 2015 19:42:20 +0800	[thread overview]
Message-ID: <201510301924.9eFzcXKi%fengguang.wu@intel.com> (raw)
In-Reply-To: <1446201391-22553-2-git-send-email-albeu@free.fr>

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

Hi Alban,

[auto build test ERROR on v4.3-rc7 -- if it's inappropriate base, please suggest rules for selecting the more suitable base]

url:    https://github.com/0day-ci/linux/commits/Alban-Bedel/MAINTAINERS-Add-an-entry-for-the-ATH79-GPIO-driver/20151030-183832
config: i386-allmodconfig (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

>> drivers/gpio/gpio-ath79.c:20:40: fatal error: asm/mach-ath79/ar71xx_regs.h: No such file or directory
   compilation terminated.

vim +20 drivers/gpio/gpio-ath79.c

6eae43c5 arch/mips/ath79/gpio.c    Gabor Juhos 2011-01-04  14  
7351d84b drivers/gpio/gpio-ath79.c Alban Bedel 2015-10-30  15  #include <linux/gpio/driver.h>
2ddf3a79 arch/mips/ath79/gpio.c    Alban Bedel 2015-05-31  16  #include <linux/platform_data/gpio-ath79.h>
2ddf3a79 arch/mips/ath79/gpio.c    Alban Bedel 2015-05-31  17  #include <linux/of_device.h>
7351d84b drivers/gpio/gpio-ath79.c Alban Bedel 2015-10-30  18  #include <linux/basic_mmio_gpio.h>
6eae43c5 arch/mips/ath79/gpio.c    Gabor Juhos 2011-01-04  19  
6eae43c5 arch/mips/ath79/gpio.c    Gabor Juhos 2011-01-04 @20  #include <asm/mach-ath79/ar71xx_regs.h>
6eae43c5 arch/mips/ath79/gpio.c    Gabor Juhos 2011-01-04  21  
7351d84b drivers/gpio/gpio-ath79.c Alban Bedel 2015-10-30  22  struct ath79_gpio {
7351d84b drivers/gpio/gpio-ath79.c Alban Bedel 2015-10-30  23  	struct bgpio_chip bgc;

:::::: The code at line 20 was first introduced by commit
:::::: 6eae43c57ee92de91f6cc7c391cea97c43295da0 MIPS: ath79: add GPIOLIB support

:::::: TO: Gabor Juhos <juhosg@openwrt.org>
:::::: CC: Ralf Baechle <ralf@linux-mips.org>

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

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 51596 bytes --]

  reply	other threads:[~2015-10-30 11:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-30 10:36 [PATCH 1/3] MAINTAINERS: Add an entry for the ATH79 " Alban Bedel
2015-10-30 10:36 ` [PATCH 2/3] gpio: ath79: Move to the generic " Alban Bedel
2015-10-30 11:42   ` kbuild test robot [this message]
2015-10-31 21:02   ` Linus Walleij
2015-11-01 17:46     ` Alban
2015-11-02  8:30       ` Linus Walleij
2015-10-30 10:36 ` [PATCH 3/3] gpio: ath79: Make the driver removable Alban Bedel
2015-10-31 21:03   ` Linus Walleij
2015-10-31 20:56 ` [PATCH 1/3] MAINTAINERS: Add an entry for the ATH79 GPIO driver Linus Walleij

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=201510301924.9eFzcXKi%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=albeu@free.fr \
    --cc=gnurou@gmail.com \
    --cc=kbuild-all@01.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®