From: kbuild test robot <lkp@intel.com>
To: Corentin Labbe <clabbe.montjoie@gmail.com>
Cc: kbuild-all@lists.01.org, catalin.marinas@arm.com,
davem@davemloft.net, herbert@gondor.apana.org.au,
linux@armlinux.org.uk, mark.rutland@arm.com, mripard@kernel.org,
robh+dt@kernel.org, wens@csie.org, will@kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-sunxi@googlegroups.com,
Corentin Labbe <clabbe.montjoie@gmail.com>
Subject: Re: [PATCH v4 02/11] crypto: Add Allwinner sun8i-ce Crypto Engine
Date: Tue, 15 Oct 2019 00:32:42 +0800 [thread overview]
Message-ID: <201910150009.4PL0gO1Q%lkp@intel.com> (raw)
In-Reply-To: <20191012184852.28329-3-clabbe.montjoie@gmail.com>
Hi Corentin,
I love your patch! Perhaps something to improve:
[auto build test WARNING on cryptodev/master]
[cannot apply to v5.4-rc3 next-20191014]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Corentin-Labbe/crypto-add-sun8i-ce-driver-for-Allwinner-crypto-engine/20191014-104401
base: https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git master
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-rc1-43-g0ccb3b4-dirty
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/crypto/allwinner/sun8i-ce/sun8i-ce-core.c:415:25: sparse: sparse: symbol 'sun8i_ce_pm_ops' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2019-10-14 16:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 18:48 [PATCH v4 00/11] crypto: add sun8i-ce driver for Allwinner crypto engine Corentin Labbe
2019-10-12 18:48 ` [PATCH v4 01/11] crypto: Add allwinner subdirectory Corentin Labbe
2019-10-12 18:48 ` [PATCH v4 02/11] crypto: Add Allwinner sun8i-ce Crypto Engine Corentin Labbe
2019-10-14 16:32 ` kbuild test robot [this message]
2019-10-14 16:32 ` [RFC PATCH] crypto: sun8i_ce_pm_ops can be static kbuild test robot
2019-10-22 9:23 ` [PATCH v4 02/11] crypto: Add Allwinner sun8i-ce Crypto Engine Dan Carpenter
2019-10-22 13:22 ` Corentin Labbe
2019-10-12 18:48 ` [PATCH v4 03/11] dt-bindings: crypto: Add DT bindings documentation for " Corentin Labbe
2019-10-12 18:48 ` [PATCH v4 04/11] ARM: dts: sun8i: R40: add crypto engine node Corentin Labbe
2019-10-12 18:48 ` [PATCH v4 05/11] ARM: dts: sun8i: H3: Add Crypto Engine node Corentin Labbe
2019-10-12 18:48 ` [PATCH v4 06/11] ARM64: dts: allwinner: sun50i: Add Crypto Engine node on A64 Corentin Labbe
2019-10-12 18:48 ` [PATCH v4 07/11] ARM64: dts: allwinner: sun50i: Add crypto engine node on H5 Corentin Labbe
2019-10-12 18:48 ` [PATCH v4 08/11] ARM64: dts: allwinner: sun50i: Add Crypto Engine node on H6 Corentin Labbe
2019-10-12 18:48 ` [PATCH v4 09/11] sunxi_defconfig: add new Allwinner crypto options Corentin Labbe
2019-10-12 18:48 ` [PATCH v4 10/11] arm64: defconfig: " Corentin Labbe
2019-10-12 18:48 ` [PATCH v4 11/11] crypto: sun4i-ss: Move to Allwinner directory Corentin Labbe
2019-10-14 10:47 ` [PATCH v4 00/11] crypto: add sun8i-ce driver for Allwinner crypto engine Maxime Ripard
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=201910150009.4PL0gO1Q%lkp@intel.com \
--to=lkp@intel.com \
--cc=catalin.marinas@arm.com \
--cc=clabbe.montjoie@gmail.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mripard@kernel.org \
--cc=robh+dt@kernel.org \
--cc=wens@csie.org \
--cc=will@kernel.org \
/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).