From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Luis de Bethencourt <luisbg@osg.samsung.com>,
linux-crypto@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH] crypto: Allow drivers to build if COMPILE_TEST is enabled
Date: Wed, 14 Oct 2015 16:17:41 +0200 [thread overview]
Message-ID: <561E6405.7050905@osg.samsung.com> (raw)
In-Reply-To: <20151014140803.GA17261@gondor.apana.org.au>
Hello Herbert,
On 10/14/2015 04:08 PM, Herbert Xu wrote:
> On Wed, Oct 14, 2015 at 05:03:30AM +0800, kbuild test robot wrote:
>> Hi Javier,
>>
>> [auto build test WARNING on cryptodev/master -- if it's inappropriate base, please suggest rules for selecting the more suitable base]
>
> Javier, please make sure these warnings are fixed before you enable
> COMPILE_TEST.
>
Yes, I will. I built tested on arm32 and x86 before posting the patch
but forgot about sparse.
Getting more build coverage for the drivers will likely lead to new
build warnings like the one reported by Fengguang so I wonder if should
just desist in enabling COMPILE_TEST for drivers since I would not be
able to test in every possible setup.
On the other hand, I guess the fact that there are issues found, shows
the usefulness of COMPILE_TEST.
> Thanks,
>
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
prev parent reply other threads:[~2015-10-14 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 13:42 Javier Martinez Canillas
2015-10-13 21:03 ` kbuild test robot
2015-10-14 14:08 ` Herbert Xu
2015-10-14 14:17 ` Javier Martinez Canillas [this message]
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=561E6405.7050905@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kbuild-all@01.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=luisbg@osg.samsung.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
all inboxes | Powered by JetHome®