[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a4bfdf4c-de88-31a2-8f8d-f32c1ebdbd02@infradead.org>
Date: Wed, 5 Jun 2019 11:56:17 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: akpm@...ux-foundation.org, broonie@...nel.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, linux-next@...r.kernel.org, mhocko@...e.cz,
mm-commits@...r.kernel.org, sfr@...b.auug.org.au,
Tudor Ambarus <tudor.ambarus@...rochip.com>,
Linux Crypto Mailing List <linux-crypto@...r.kernel.org>,
linux-kbuild <linux-kbuild@...r.kernel.org>,
Masahiro Yamada <yamada.masahiro@...ionext.com>
Subject: Re: mmotm 2019-06-04-16-33 uploaded (drivers/crypto/atmel)
On 6/4/19 4:34 PM, akpm@...ux-foundation.org wrote:
> The mm-of-the-moment snapshot 2019-06-04-16-33 has been uploaded to
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of my -mm patch queue. Uploaded at random hopefully
> more than once a week.
>
(problem seen in mmotm, but this is not an mmotm patch; it's from linux-next)
on x86_64:
ld: drivers/crypto/atmel-i2c.o: in function `atmel_i2c_checksum':
atmel-i2c.c:(.text+0x1b): undefined reference to `crc16'
because CONFIG_CRC16=m and CONFIG_CRYPTO_DEV_ATMEL_I2C=y.
The latter selects the former.
I don't know how to make CRC16 be builtin in this case. ???
I changed the 'select' to 'imply' but that didn't make any difference.
Full randconfig file is attached.
thanks.
--
~Randy
View attachment "config-r5631" of type "text/plain" (122778 bytes)
Powered by blists - more mailing lists