From: Randy Dunlap <rdunlap@infradead.org>
To: Herbert Xu <herbert@gondor.hengli.com.au>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Jonathan Cameron <jic23@cam.ac.uk>,
linux-iio@vger.kernel.org, Artem Bityutskiy <dedekind1@gmail.com>,
linux-mtd@lists.infradead.org, linux-crypto@vger.kernel.org
Subject: Re: linux-next: Tree for Jan 23 (mtd/ubi and iio and crypto/crc32[c])
Date: Wed, 23 Jan 2013 15:41:57 -0800 [thread overview]
Message-ID: <51007545.5040406@infradead.org> (raw)
In-Reply-To: <20130123232316.GB25726@gondor.apana.org.au>
On 01/23/13 15:23, Herbert Xu wrote:
> On Wed, Jan 23, 2013 at 03:10:01PM -0800, Randy Dunlap wrote:
>> On 01/22/13 22:43, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20130122:
>>>
>>
>>
>> on i386:
>>
>> ERROR: "crc32_le" [drivers/mtd/ubi/ubi.ko] undefined!
>> ERROR: "iio_triggered_buffer_setup" [drivers/iio/adc/max1363.ko] undefined!
>> ERROR: "iio_triggered_buffer_cleanup" [drivers/iio/adc/max1363.ko] undefined!
>> ERROR: "__crc32c_le" [crypto/crc32c.ko] undefined!
>> ERROR: "crc32_le" [crypto/crc32.ko] undefined!
>
> Weird. You do have CONFIG_CRC32 selected, so did it compile
> a lib/crc32.ko or not?
Hmph, this seems to be some kind of rebuild problem. It's not
reproducible, so the mtd/ubi and crypto reports above are incorrect --
please ignore them. Only the iio one is reproducible.
Sorry about that.
--
~Randy
next prev parent reply other threads:[~2013-01-23 23:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 6:43 linux-next: Tree for Jan 23 Stephen Rothwell
2013-01-23 22:18 ` Stephen Rothwell
2013-01-23 23:10 ` linux-next: Tree for Jan 23 (mtd/ubi and iio and crypto/crc32[c]) Randy Dunlap
2013-01-23 23:23 ` Herbert Xu
2013-01-23 23:41 ` Randy Dunlap [this message]
2013-01-26 10:02 ` Jonathan Cameron
2013-01-23 23:28 ` linux-next: Tree for Jan 23 (pch_uart.c) Randy Dunlap
2013-01-24 2:06 ` Stephen Rothwell
2013-01-24 2:30 ` Liang Li
2013-01-24 4:15 ` Stephen Rothwell
2013-01-24 4:25 ` Liang Li
2013-01-23 23:56 ` linux-next: Tree for Jan 23 (hvc and virtio_console) Randy Dunlap
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=51007545.5040406@infradead.org \
--to=rdunlap@infradead.org \
--cc=dedekind1@gmail.com \
--cc=herbert@gondor.hengli.com.au \
--cc=jic23@cam.ac.uk \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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).