From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756714AbbKRTy4 (ORCPT ); Wed, 18 Nov 2015 14:54:56 -0500 Received: from mout.kundenserver.de ([212.227.126.135]:64507 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755237AbbKRTyy (ORCPT ); Wed, 18 Nov 2015 14:54:54 -0500 From: Arnd Bergmann To: kbuild test robot Cc: kbuild-all@01.org, Herbert Xu , linux-crypto@vger.kernel.org, Leilei Zhao , Nicolas Ferre , linux-arm-kernel@lists.infradead.org, Ludovic Desroches , linux-kernel@vger.kernel.org, Alexandre Belloni Subject: Re: [PATCH v3] crypto: atmel: fix bogus select Date: Wed, 18 Nov 2015 20:54:03 +0100 Message-ID: <3878434.NqzKGChk39@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <201511190227.fHF3LVfw%fengguang.wu@intel.com> References: <201511190227.fHF3LVfw%fengguang.wu@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:VxhjCdfpTtpEpqiDvIQu2lx0Xg59tAKAqyNjXKZ6WxvGCGk406l GLU0lnEaF1CBd+5apWMX2y8opbLZCKeoo2T9K4r1xt3Se0SeLJqF9tkmOdTKtIks5LbLYAx yKNQQDBzw0zqSPWKw+9hXeBsxgp+d90Y8dozv7pQA/ObKONPxDxKXhZ3Vt0VTlISgL+Rc43 WJgyKyoRi4UT0wsaph6ng== X-UI-Out-Filterresults: notjunk:1;V01:K0:b+kHtOxV4zQ=:xMIv16wO0Qz35wMs6urqa7 p/rURa00ZF8QSVDQx3FqQk8fI26FKddry5rart0RxcxhY4qbiTr8pAeRvDEvnAQiUe3zjr7PR oj/XdLkja5ByZqV2RtCd6qiPpavr9aG02V+tRtf+bHllt1vYLLd1tNtn9+f1ADlvfFy/l4Hyp aFHLiCxLK7mLeuGOoh0cgZjFmVW2fhmZLgQp+r22gFA79nsNFYR/WFYEAa32TYuPAMgUm7t6z rfoea3CVMFYqMs9gZHGLp2slZzp8H5YvZnsiQqLsVbIm7WHm01YIlR1QsgHxtTpIn5hRak8Ei sWDigqEta+6LNcRDT/gCDDaz/8e2nsM0LKiq4z0e+XOJhsYErhFnHHN42kxYa+4KWWHRhvTNH OsHHY7ZLPDhp8C+KEuEDOM/Rp8mgU2FID+dBDn6zYfBjTIqTzpcoyH0gKJ/95/xWm5A2Bg37N pnJhP/32LeJc0Upf38IIwrqtdM/PVyX/Q9HcP0y10RajTbmN8+RICalXPEWFnAdCAFukCo1jy sZpyOtx/I8E9hT3WIg4sqvsh1sHetSylKBTXvkjJltrtR9S118SSEgpBIsuZ3R8p63sIhIWFt IZykk9lmmUCO824IBJikvscUlV7LpoS28uWppUamR7STRND62If12Gb4Ijud3V70ey2RrzlQC 4a5g6cW2ZgChbYjKLQmK0Pdy0MzlafjtCySmU367VSyF2tXrq/UzH9x3lv8pn8zFkjgTt1X0y V+YFaGkiaGKP5m7b Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thursday 19 November 2015 02:17:21 kbuild test robot wrote: > > [auto build test WARNING on: cryptodev/master] > [also build test WARNING on: v4.4-rc1 next-20151118] > > url: https://github.com/0day-ci/linux/commits/Arnd-Bergmann/crypto-atmel-fix-bogus-select/20151118-233706 > base: https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git master > config: tile-allmodconfig (attached as .config) > reproduce: > wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross > chmod +x ~/bin/make.cross > # save the attached .config to linux build tree > make.cross ARCH=tile > > All warnings (new ones prefixed by >>): > > drivers/crypto/atmel-aes.c: In function 'atmel_aes_sg_copy': > >> drivers/crypto/atmel-aes.c:191:11: warning: comparison of distinct pointer types lacks a cast [enabled by default] > drivers/crypto/atmel-aes.c: In function 'atmel_aes_crypt_dma_start': > drivers/crypto/atmel-aes.c:447:11: warning: comparison of distinct pointer types lacks a cast [enabled by default] > drivers/crypto/atmel-aes.c:448:11: warning: comparison of distinct pointer types lacks a cast [enabled by default] > drivers/crypto/atmel-aes.c: In function 'atmel_aes_crypt_dma_stop': > >> drivers/crypto/atmel-aes.c:642:5: warning: format '%u' expects argument of type 'unsigned int', but argument 2 has type 'size_t' [-Wformat] > drivers/crypto/atmel-aes.c: In function 'atmel_aes_buff_init': > >> drivers/crypto/atmel-aes.c:669:3: warning: format '%d' expects argument of type 'int', but argument 3 has type 'size_t' [-Wformat] > drivers/crypto/atmel-aes.c:677:3: warning: format '%d' expects argument of type 'int', but argument 3 has type 'size_t' [-Wformat] > > Thanks for the report. I actually submitted a patch for these yesterday, but I should have realized now that there is a dependency between the two patches, and the other one needs to be applied first to avoid generating these warnings in allmodconfig builds for all architectures. Arnd