From: Fengguang Wu <fengguang.wu@intel.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Huang Shijie <b32955@freescale.com>,
linux-mtd@lists.infradead.org, kbuild-all@01.org
Subject: Re: [l2-mtd:spinor 125/128] ERROR: "spi_nor_ids" [drivers/mtd/devices/m25p80.ko] undefined!
Date: Wed, 9 Apr 2014 13:31:40 +0800 [thread overview]
Message-ID: <20140409053140.GB29432@localhost> (raw)
In-Reply-To: <20140409050515.GA4400@brian-ubuntu>
On Tue, Apr 08, 2014 at 10:05:15PM -0700, Brian Norris wrote:
> On Wed, Apr 09, 2014 at 12:36:26PM +0800, Huang Shijie wrote:
> > 于 2014年04月09日 11:42, kbuild test robot 写道:
> >
> > >tree: git://git.infradead.org/users/dedekind/l2-mtd.git spinor
>
> Wow, you build every branch, not just those in -next?
Yes, the 0day robot tests virtually every branch in ~400 git trees to
catch bugs as early as possible.
Thanks,
Fengguang
prev parent reply other threads:[~2014-04-09 5:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5344c1be.z3phCxZtgQ0NsWcF%fengguang.wu@intel.com>
[not found] ` <5344CE4A.2000003@freescale.com>
2014-04-09 5:05 ` [l2-mtd:spinor 125/128] ERROR: "spi_nor_ids" [drivers/mtd/devices/m25p80.ko] undefined! Brian Norris
2014-04-09 5:31 ` Fengguang Wu [this message]
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=20140409053140.GB29432@localhost \
--to=fengguang.wu@intel.com \
--cc=b32955@freescale.com \
--cc=computersforpeace@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-mtd@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).