From: kbuild test robot <lkp@intel.com>
To: Alison Wang <b18965@freescale.com>
Cc: kbuild-all@01.org, cyrille.pitchen@atmel.com,
marek.vasut@gmail.com, computersforpeace@gmail.com,
dwmw2@infradead.org, boris.brezillon@free-electrons.com,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, alison.wang@nxp.com
Subject: Re: [PATCH] mtd: nand: Update dependency of IFC for LS1021A
Date: Thu, 29 Dec 2016 17:52:37 +0800 [thread overview]
Message-ID: <201612291704.0tMw9Uis%fengguang.wu@intel.com> (raw)
In-Reply-To: <1482973102-47659-1-git-send-email-b18965@freescale.com>
[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]
Hi Alison,
[auto build test WARNING on mtd/master]
[also build test WARNING on v4.10-rc1 next-20161224]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Alison-Wang/mtd-nand-Update-dependency-of-IFC-for-LS1021A/20161229-125233
base: git://git.infradead.org/linux-mtd.git master
config: arm-allmodconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1 20160705
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 warnings (new ones prefixed by >>):
warning: (MTD_NAND_FSL_IFC) selects FSL_IFC which has unmet direct dependencies (MEMORY && (FSL_SOC || ARCH_LAYERSCAPE))
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 59438 bytes --]
next prev parent reply other threads:[~2016-12-29 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 0:58 [PATCH] mtd: nand: Update dependency of IFC for LS1021A Alison Wang
2016-12-29 9:52 ` kbuild test robot [this message]
2017-01-02 9:01 ` Boris Brezillon
2017-01-03 1:24 ` Alison Wang
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=201612291704.0tMw9Uis%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=alison.wang@nxp.com \
--cc=b18965@freescale.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@atmel.com \
--cc=dwmw2@infradead.org \
--cc=kbuild-all@01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.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