All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Amitkumar Karwar <akarwar@marvell.com>
Cc: kbuild-all@01.org, linux-wireless@vger.kernel.org,
	Cathy Luo <cluo@marvell.com>,
	Nishant Sarmukadam <nishants@marvell.com>,
	Xinming Hu <huxm@marvell.com>,
	Amitkumar Karwar <akarwar@marvell.com>
Subject: Re: [PATCH 2/4] mwifiex: enable pcie MSIx interrupt mode support
Date: Fri, 1 Jan 2016 02:03:16 +0800	[thread overview]
Message-ID: <201601010258.TdInjVcJ%fengguang.wu@intel.com> (raw)
In-Reply-To: <1451571855-29449-2-git-send-email-akarwar@marvell.com>

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

Hi Xinming,

[auto build test ERROR on wireless-drivers-next/master]
[also build test ERROR on next-20151231]
[cannot apply to v4.4-rc7]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]

url:    https://github.com/0day-ci/linux/commits/Amitkumar-Karwar/mwifiex-fix-missing-debug-messages/20151231-222922
base:   https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.git master
config: mips-allyesconfig (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=mips 

All errors (new ones prefixed by >>):

   In file included from drivers/net/wireless/marvell/mwifiex/main.h:45:0,
                    from drivers/net/wireless/marvell/mwifiex/main.c:20:
>> drivers/net/wireless/marvell/mwifiex/pcie.h:342:20: error: array type has incomplete element type 'struct msix_entry'
     struct msix_entry msix_entries[MWIFIEX_NUM_MSIX_VECTORS];
                       ^

vim +342 drivers/net/wireless/marvell/mwifiex/pcie.h

   336		u8 *sleep_cookie_vbase;
   337		dma_addr_t sleep_cookie_pbase;
   338		void __iomem *pci_mmap;
   339		void __iomem *pci_mmap1;
   340		int msi_enable;
   341		int msix_enable;
 > 342		struct msix_entry msix_entries[MWIFIEX_NUM_MSIX_VECTORS];
   343		struct mwifiex_msix_context msix_ctx[MWIFIEX_NUM_MSIX_VECTORS];
   344		struct mwifiex_msix_context share_irq_ctx;
   345	};

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

  parent reply	other threads:[~2015-12-31 18:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-31 14:24 [PATCH 1/4] mwifiex: fix missing debug messages Amitkumar Karwar
2015-12-31 14:24 ` [PATCH 2/4] mwifiex: enable pcie MSIx interrupt mode support Amitkumar Karwar
2015-12-31 16:31   ` kbuild test robot
2015-12-31 18:03   ` kbuild test robot [this message]
2016-01-05 12:57     ` Amitkumar Karwar
2016-01-07  9:17   ` Kalle Valo
2015-12-31 14:24 ` [PATCH 3/4] mwifiex: increase priority for critical message Amitkumar Karwar
2015-12-31 14:24 ` [PATCH 4/4] mwifiex: reduce cloned skb queue size Amitkumar Karwar
2016-01-07  9:15 ` [1/4] mwifiex: fix missing debug messages Kalle Valo

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=201601010258.TdInjVcJ%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=akarwar@marvell.com \
    --cc=cluo@marvell.com \
    --cc=huxm@marvell.com \
    --cc=kbuild-all@01.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nishants@marvell.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.