[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170329083002.GT6986@localhost.localdomain>
Date: Wed, 29 Mar 2017 09:30:02 +0100
From: Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
To: <broonie@...nel.org>, <lee.jones@...aro.org>
CC: <mark.rutland@....com>, <devicetree@...r.kernel.org>,
<alsa-devel@...a-project.org>,
<patches@...nsource.wolfsonmicro.com>, <lgirdwood@...il.com>,
<linux-kernel@...r.kernel.org>, <robh+dt@...nel.org>
Subject: Re: [alsa-devel] [PATCH v2 6/8] regulator: arizona-micbias: Add
regulator driver for Arizona micbiases
On Wed, Mar 29, 2017 at 02:18:23PM +0800, kbuild test robot wrote:
> Hi Charles,
>
> [auto build test WARNING on regulator/for-next]
> [also build test WARNING on v4.11-rc4 next-20170328]
> [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/Charles-Keepax/regulator-arizona-micsupp-Avoid-potential-memory-leak-reading-init_data/20170329-112224
> base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
> config: i386-randconfig-x0-03291136 (attached as .config)
> compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=i386
>
Hmm... this is due to the tree missing the patch that Lee already
applied from version 1. I guess perhaps we should pull that back
into this series or he could make an immutable branch you can pull
in?
Thanks,
Charles
Powered by blists - more mailing lists