linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mtd: nand: Update dependency of IFC for LS1021A
Date: Mon, 2 Jan 2017 10:01:24 +0100	[thread overview]
Message-ID: <20170102100124.78ca7d7e@bbrezillon> (raw)
In-Reply-To: <201612291704.0tMw9Uis%fengguang.wu@intel.com>

Hi Alison,

On Thu, 29 Dec 2016 17:52:37 +0800
kbuild test robot <lkp@intel.com> wrote:

> 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))

Do you have another patch adding the '||?SOC_LS1021A' dependency on
FSL_IFC? If so, please send both patches in the same series.

Thanks,

Boris

  reply	other threads:[~2017-01-02  9:01 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
2017-01-02  9:01   ` Boris Brezillon [this message]
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=20170102100124.78ca7d7e@bbrezillon \
    --to=boris.brezillon@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.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).