From: Dinh Nguyen <dinguyen@altera.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Artem Bityutskiy <dedekind1@gmail.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the l2-mtd tree
Date: Thu, 11 Oct 2012 22:51:19 -0600 [thread overview]
Message-ID: <1350017479.22202.2.camel@dinh-ubuntu> (raw)
In-Reply-To: <20121012111451.ad2a5db59d470cf24393226a@canb.auug.org.au>
Hi Stephen,
On Fri, 2012-10-12 at 11:14 +1100, Stephen Rothwell wrote:
> Hi Artem,
>
> After merging the l2-mtd tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> ERROR: "denali_init" [drivers/mtd/nand/denali_pci.ko] undefined!
> ERROR: "denali_remove" [drivers/mtd/nand/denali_pci.ko] undefined!
>
> Probably caused by commit 305b1ee29c8e ("mtd: denali: split the generic
> driver and PCI layer").
>
> I have used the l2-mtd tree from next-20121011 for today.
Sorry about that. I just sent a patch to fix this. Please disregard the
first email, I forgot to include Artem in the email.
Thanks,
Dinh
next prev parent reply other threads:[~2012-10-12 3:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 0:14 linux-next: build failure after merge of the l2-mtd tree Stephen Rothwell
2012-10-12 4:51 ` Dinh Nguyen [this message]
2012-10-18 0:28 ` Stephen Rothwell
2012-10-18 9:26 ` Artem Bityutskiy
-- strict thread matches above, loose matches on Subject: below --
2017-08-28 2:19 Stephen Rothwell
2017-08-28 22:06 ` Brian Norris
2017-02-09 1:08 Stephen Rothwell
2017-02-09 1:59 ` Brian Norris
2016-07-19 0:59 Stephen Rothwell
2016-07-19 1:20 ` Brian Norris
2016-07-19 1:46 ` Stephen Rothwell
2015-12-21 5:47 Stephen Rothwell
2015-09-30 5:16 Stephen Rothwell
2014-05-22 5:30 Stephen Rothwell
2014-05-26 17:42 ` Brian Norris
2014-05-26 23:59 ` Stephen Rothwell
2014-05-27 10:40 ` Artem Bityutskiy
2014-05-27 22:49 ` Stephen Rothwell
2012-02-07 2:58 Stephen Rothwell
2012-02-07 8:02 ` Artem Bityutskiy
2012-02-06 1:07 Stephen Rothwell
2012-02-06 9:14 ` Artem Bityutskiy
2012-02-06 21:10 ` Stephen Rothwell
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=1350017479.22202.2.camel@dinh-ubuntu \
--to=dinguyen@altera.com \
--cc=dedekind1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).