[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170228213149.GA6651@roeck-us.net>
Date: Tue, 28 Feb 2017 13:31:49 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: Arnd Bergmann <arnd@...db.de>
Cc: Wim Van Sebroeck <wim@...ana.be>, linux-watchdog@...r.kernel.org,
Lee Jones <lee.jones@...aro.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/8] watchdog fixes for COMPILE_TEST change
On Tue, Feb 28, 2017 at 10:01:15PM +0100, Arnd Bergmann wrote:
> Hi Guenter,
>
> I noticed your change to enable lots of watchdog drivers for compile
> testing in linux-next today. While this is generally a great idea,
> I'm not entirely sure why this appeared during the merge window.
>
Problem is that Wim doesn't apply patches to a tree which gets exposed
to -next. I'll have to discuss with him how to change that. The tree
has been exposed to 0day for quite some time, though, which did not
report any errors (nor did my own build tests). No idea how both me
and 0day missed all those problems.
Sorry :-(
Guenter
> I case you plan to have this merged into v4.11, please make sure
> to get the fixups in. I found eight drivers that now have incorrect
> dependencies. For two of them I changed the MFD code, for the others
> I just adapted the Kconfig dependencies, mostly by reverting
> part of your patch.
>
> Arnd
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists