[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5103A9C2.40206@cam.ac.uk>
Date: Sat, 26 Jan 2013 10:02:42 +0000
From: Jonathan Cameron <jic23@....ac.uk>
To: Randy Dunlap <rdunlap@...radead.org>
CC: Herbert Xu <herbert@...dor.apana.org.au>,
Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-iio@...r.kernel.org, Artem Bityutskiy <dedekind1@...il.com>,
linux-mtd@...ts.infradead.org, linux-crypto@...r.kernel.org
Subject: Re: linux-next: Tree for Jan 23 (mtd/ubi and iio and crypto/crc32[c])
On 01/23/2013 11:41 PM, Randy Dunlap wrote:
> 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.
>
For iio one had a patch for a while, just not had a chance to send
a pull request to Greg until today. Sorry for the slow response.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists