netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: igal.liberman@freescale.com
Cc: kbuild-all@01.org, netdev@vger.kernel.org, pebolle@tiscali.nl,
	linux-kernel@vger.kernel.org, ppc@mindchasers.com,
	stephen@networkplumber.org,
	Igal Liberman <igal.liberman@freescale.com>,
	scottwood@freescale.com, linuxppc-dev@lists.ozlabs.org,
	davem@davemloft.net, madalin.bucur@freescale.com
Subject: Re: [v6, 5/6] fsl/fman: Add FMan Port Support
Date: Thu, 29 Oct 2015 17:49:09 +0800	[thread overview]
Message-ID: <201510291741.GxLZbj2r%fengguang.wu@intel.com> (raw)
In-Reply-To: <1446022429-31621-6-git-send-email-igal.liberman@freescale.com>

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

Hi Igal,

[auto build test ERROR on net/master -- if it's inappropriate base, please suggest rules for selecting the more suitable base]

url:    https://github.com/0day-ci/linux/commits/igal-liberman-freescale-com/Freescale-DPAA-FMan/20151028-205843
config: arm-allmodconfig (attached as .config)
reproduce:
        wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=arm 

All errors (new ones prefixed by >>):

>> drivers/net/ethernet/freescale/fman/fman_port.c:39:25: fatal error: asm/mpc85xx.h: No such file or directory
    #include <asm/mpc85xx.h>
                            ^
   compilation terminated.

vim +39 drivers/net/ethernet/freescale/fman/fman_port.c

    33	#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
    34	
    35	#include "fman_port.h"
    36	#include "fman.h"
    37	#include "fman_sp.h"
    38	
  > 39	#include <asm/mpc85xx.h>
    40	#include <linux/io.h>
    41	#include <linux/slab.h>
    42	#include <linux/module.h>

---
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: 53727 bytes --]

  reply	other threads:[~2015-10-29  9:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-28  8:53 [v6, 0/6] Freescale DPAA FMan igal.liberman
2015-10-28  8:53 ` [v6, 1/6] fsl/fman: Add FMan MURAM support igal.liberman
2015-10-28  8:53 ` [v6, 2/6] fsl/fman: Add FMan support igal.liberman
2015-10-29  8:29   ` kbuild test robot
2015-10-28  8:53 ` [v6, 3/6] fsl/fman: Add FMan MAC support igal.liberman
2015-10-29  9:09   ` kbuild test robot
2015-10-28  8:53 ` [v6, 4/6] fsl/fman: Add FMan SP support igal.liberman
2015-10-28  8:53 ` [v6, 5/6] fsl/fman: Add FMan Port Support igal.liberman
2015-10-29  9:49   ` kbuild test robot [this message]
2015-10-28  8:53 ` [v6, 6/6] fsl/fman: Add FMan MAC driver igal.liberman
2015-10-29 10:21   ` kbuild 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=201510291741.GxLZbj2r%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=davem@davemloft.net \
    --cc=igal.liberman@freescale.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=madalin.bucur@freescale.com \
    --cc=netdev@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    --cc=ppc@mindchasers.com \
    --cc=scottwood@freescale.com \
    --cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).