All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Luis de Bethencourt <luisbg@osg.samsung.com>,
	linux-kernel@vger.kernel.org
Cc: linux-watchdog@vger.kernel.org, wim@iguana.be, javier@osg.samsung.com
Subject: Re: [PATCH v2] watchdog: Compile possible drivers with COMPILE_TEST
Date: Wed, 14 Oct 2015 15:40:38 -0700	[thread overview]
Message-ID: <561ED9E6.8070600@roeck-us.net> (raw)
In-Reply-To: <561ED31C.7090605@osg.samsung.com>

On 10/14/2015 03:11 PM, Luis de Bethencourt wrote:
> On 14/10/15 22:35, Guenter Roeck wrote:
>> On 10/14/2015 11:55 AM, Luis de Bethencourt wrote:
>>> These drivers have depends that aren't build dependencies, so it's
>>> a good idea to allow these drivers to always be built when the
>>> COMPILE_TEST option is enabled.
>>>
>>> That way, the drivers can be built with a config generated by make
>>> allyesconfig and check if a patch would break the build.
>>>
>>> Signed-off-by: Luis de Bethencourt <luisbg@osg.samsung.com>
>>
>> What architectures have you actually tested this for ?
>>
>> Guenter
>>
>
> I've compiled it in x86 and then I tried ARM
> (with CROSS_COMPILE="ccache arm-linux-gnueabihf-" ARCH=arm)
>
> But ARM kept failing due to other drivers, first Lustre then an Ethernet
> driver (I40E), and more.
>
arm:allmodconfig should build fine. Either case, you can always run "make -i"
to ignore errors, to ensure that you at least don't introduce new problems.

> Is there a better way of doing this?
>
Sure, at least run allmodconfig for _all_ architectures, or at least
for the major architectures.

Guenter


  reply	other threads:[~2015-10-14 22:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 18:55 [PATCH v2] watchdog: Compile possible drivers with COMPILE_TEST Luis de Bethencourt
2015-10-14 21:35 ` Guenter Roeck
2015-10-14 22:11   ` Luis de Bethencourt
2015-10-14 22:40     ` Guenter Roeck [this message]
2015-10-15  2:11       ` Krzysztof Kozlowski
2015-10-16 13:05         ` Luis de Bethencourt
2015-10-16  4:11 ` kbuild test robot

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=561ED9E6.8070600@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=javier@osg.samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=luisbg@osg.samsung.com \
    --cc=wim@iguana.be \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.