From: Rob Herring <robh@kernel.org>
To: anilc@codeaurora.org
Cc: kbuild test robot <lkp@intel.com>,
kbuild-all@01.org, andy.gross@linaro.org, david.brown@linaro.org,
mark.rutland@arm.com, herbert@gondor.apana.org.au,
davem@davemloft.net, linux-soc@vger.kernel.org,
devicetree@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] crypto: qce: ice: Add support for Inline Crypto Engine
Date: Thu, 25 Oct 2018 09:58:41 -0500 [thread overview]
Message-ID: <20181025145841.GB30244@bogus> (raw)
In-Reply-To: <d6f1930a618f6539a4c3e53d239fdd90@codeaurora.org>
On Wed, Oct 24, 2018 at 04:44:37PM +0530, anilc@codeaurora.org wrote:
> Hi,
>
> Thanks for the comments, response inline.
FYI, this was from a bot.
>
> Thanks,
> AnilKumar
>
>
> On 2018-10-18 17:13, kbuild test robot wrote:
> > Hi AnilKumar,
> >
> > Thank you for the patch! Yet something to improve:
> >
> > [auto build test ERROR on cryptodev/master]
> > [also build test ERROR on v4.19-rc8 next-20181018]
> > [if your patch is applied to the wrong git tree, please drop us a note
> > to help improve the system]
> >
> > url:
> > https://github.com/0day-ci/linux/commits/AnilKumar-Chimata/firmware-qcom-scm-Update-qcom_scm_call-signature/20181018-182318
> > base:
> > https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git
> > master
> > config: sh-allmodconfig (attached as .config)
> > compiler: sh4-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
> > reproduce:
> > wget
> > https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross
> > -O ~/bin/make.cross
> > chmod +x ~/bin/make.cross
> > # save the attached .config to linux build tree
> > GCC_VERSION=7.2.0 make.cross ARCH=sh
> >
> > All errors (new ones prefixed by >>):
> >
> > > > drivers/crypto/qce/ice.c:1372:5: error: redefinition of
> > > > 'qcom_ice_setup_ice_hw'
> > int qcom_ice_setup_ice_hw(const char *storage_type, int enable)
> > ^~~~~~~~~~~~~~~~~~~~~
> > In file included from drivers/crypto/qce/ice.c:25:0:
> > include/crypto/ice.h:60:19: note: previous definition of
> > 'qcom_ice_setup_ice_hw' was here
> > static inline int qcom_ice_setup_ice_hw(const char *storage_type,
> > int enable)
> > ^~~~~~~~~~~~~~~~~~~~~
> >
> > vim +/qcom_ice_setup_ice_hw +1372 drivers/crypto/qce/ice.c
> >
> > 1371
> > > 1372 int qcom_ice_setup_ice_hw(const char *storage_type, int enable)
> > 1373 {
> > 1374 struct ice_device *ice_dev = NULL;
> > 1375 int ret = -1;
> > 1376
> > 1377 ice_dev = get_ice_device_from_storage_type(storage_type);
> > 1378 if (ice_dev == ERR_PTR(-EPROBE_DEFER))
> > 1379 return -EPROBE_DEFER;
> > 1380
> > 1381 if (!ice_dev)
> > 1382 return ret;
> > 1383
> > 1384 if (enable)
> > 1385 return enable_ice_setup(ice_dev);
> > 1386
> > 1387 return disable_ice_setup(ice_dev);
> > 1388 }
> > 1389
>
> We will check and get back on the compilation. What is the idea behind for
> this
> effort, is this for testing the ICE driver?
The purpose is to make sure changes don't break builds that you likely
haven't tested. Either different architectures or configurations.
Rob
next prev parent reply other threads:[~2018-10-25 14:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 15:17 [PATCH 0/3] Add Inline Crypto Engine (ICE) driver AnilKumar Chimata
2018-10-17 15:17 ` [PATCH 1/3] firmware: qcom: scm: Update qcom_scm_call signature AnilKumar Chimata
2018-10-17 15:17 ` [PATCH 2/3] dt-bindings: Add ICE device specific parameters AnilKumar Chimata
2018-10-25 18:15 ` Rob Herring
2018-10-29 13:30 ` AnilKumar Chimata
2018-10-17 15:17 ` [PATCH 3/3] crypto: qce: ice: Add support for Inline Crypto Engine AnilKumar Chimata
2018-10-17 17:04 ` Theodore Y. Ts'o
2018-10-24 12:04 ` AnilKumar Chimata
2018-10-17 17:39 ` Randy Dunlap
2018-10-24 14:43 ` AnilKumar Chimata
2018-10-18 11:43 ` kbuild test robot
2018-10-24 11:14 ` anilc
2018-10-25 14:58 ` Rob Herring [this message]
2018-10-29 13:31 ` AnilKumar Chimata
2018-10-25 14:55 ` Rob Herring
2018-10-25 15:28 ` Theodore Y. Ts'o
2018-10-25 15:45 ` Rob Herring
2018-10-29 13:47 ` AnilKumar Chimata
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=20181025145841.GB30244@bogus \
--to=robh@kernel.org \
--cc=andy.gross@linaro.org \
--cc=anilc@codeaurora.org \
--cc=davem@davemloft.net \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=kbuild-all@01.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mark.rutland@arm.com \
/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).