On 01/08/18 17:02, Mark Brown wrote:
On Wed, Aug 01, 2018 at 04:44:03PM +0100, Guillaume Tucker wrote:
On 31/07/18 16:14, kernelci.org bot wrote:
[...]> bcm2837-rpi-3-b:
lab-baylibre: failing since 1 day (last pass: next-20180727 - first fail: next-20180730)
I've run an automated bisection on kernelci.org which found
this "bad" commit:
bb4b894addb09a069c072a0a032f644cc470d17f is the first bad commit
commit bb4b894addb09a069c072a0a032f644cc470d17f
Author: Srinivas Kandagatla <srinivas.kandagatla@xxxxxxxxxx>
Date: Fri Jul 13 16:36:28 2018 +0100
ASoC: core: add support to card re-bind using component framework
This patch aims at achieving dynamic behaviour of audio card when
the dependent components disappear and reappear.
(something in your mail client or workflow mangled the commit log here).
I'm somewhat suspicious of this result given that that commit has been
in -next rather longer than one day and the board doesn't visibly have a
sound card in mainline (there are some I2S controllers in there but no
card to use them).
Indeed, this bisection was run with CONFIG_MODULES disabled which
may have caused this. So although it's a bit surprising that it
failed to boot with modules disabled, please discard the
bisection result as far as regular boot tests are concerned.
Best wishes,
Guillaume
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
