From: kbuild test robot <lkp@intel.com>
To: Jiancheng Xue <xuejiancheng@huawei.com>
Cc: kbuild-all@01.org, robh+dt@kernel.org, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org, dwmw2@infradead.org,
computersforpeace@gmail.com, shijie.huang@intel.com,
pengbinquan@huawei.com, xuejiancheng@huawei.com,
han.xu@freescale.com, ezequiel@vanguardiasur.com.ar,
fabio.estevam@freescale.com, manabian@gmail.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mtd@lists.infradead.org, yanhaifeng@hisilicon.com,
yanghongwei@hisilicon.com, suwenping@hisilicon.com,
raojun@hisilicon.com, ml.yang@hisilicon.com,
gaofei@hisilicon.com, zhangzhenxing@hisilicon.com,
xuejiancheng@hisilicon.com
Subject: Re: [PATCH v4] mtd: spi-nor: add hisilicon spi-nor flash controller driver
Date: Mon, 25 Jan 2016 22:16:08 +0800 [thread overview]
Message-ID: <201601252239.BwD6L9lH%fengguang.wu@intel.com> (raw)
In-Reply-To: <1453704460-8956-1-git-send-email-xuejiancheng@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 1395 bytes --]
Hi Jiancheng,
[auto build test ERROR on v4.5-rc1]
[also build test ERROR on next-20160125]
[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/Jiancheng-Xue/mtd-spi-nor-add-hisilicon-spi-nor-flash-controller-driver/20160125-150412
config: arm64-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=arm64
All errors (new ones prefixed by >>):
drivers/mtd/spi-nor/hisi-sfc.c: In function 'hisi_spi_nor_probe':
>> drivers/mtd/spi-nor/hisi-sfc.c:423:6: error: 'struct spi_nor' has no member named 'flash_node'
nor->flash_node = np;
^
vim +423 drivers/mtd/spi-nor/hisi-sfc.c
417 struct mtd_info *mtd = &nor->mtd;
418 struct mtd_partition *parts = NULL;
419 int nr_parts = 0;
420
421 mtd->name = np->name;
422 nor->dev = dev;
> 423 nor->flash_node = np;
424 ret = of_property_read_u32(np, "reg", &priv->chipselect);
425 if (ret)
426 goto fail;
---
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: 48153 bytes --]
next prev parent reply other threads:[~2016-01-25 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 6:47 Jiancheng Xue
2016-01-25 14:16 ` kbuild test robot [this message]
2016-01-26 2:46 ` Rob Herring
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=201601252239.BwD6L9lH%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=fabio.estevam@freescale.com \
--cc=galak@codeaurora.org \
--cc=gaofei@hisilicon.com \
--cc=han.xu@freescale.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=manabian@gmail.com \
--cc=mark.rutland@arm.com \
--cc=ml.yang@hisilicon.com \
--cc=pawel.moll@arm.com \
--cc=pengbinquan@huawei.com \
--cc=raojun@hisilicon.com \
--cc=robh+dt@kernel.org \
--cc=shijie.huang@intel.com \
--cc=suwenping@hisilicon.com \
--cc=xuejiancheng@hisilicon.com \
--cc=xuejiancheng@huawei.com \
--cc=yanghongwei@hisilicon.com \
--cc=yanhaifeng@hisilicon.com \
--cc=zhangzhenxing@hisilicon.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
all inboxes | Powered by JetHome®