[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ED290C750E1B324E972B0017C9D4BAB01FDD5370@USCULXMSG01.am.sony.com>
Date: Mon, 1 May 2017 21:20:50 +0000
From: "Rowand, Frank" <Frank.Rowand@...y.com>
To: Rob Herring <robh+dt@...nel.org>
CC: Stephen Boyd <stephen.boyd@...aro.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Frank Rowand <frowand.list@...il.com>
Subject: RE: [PATCH] of: undeclared variable when CONFIG_DEBUG_LOCK_ALLOC
On Monday, May 01, 2017 1:13 PM, Rob Herring [mailto:robh+dt@...nel.org] wrote:
>
> On Sun, Apr 30, 2017 at 3:00 PM, Frank Rowand <frank.rowand@...y.com>
> wrote:
>> An undeclared variable was used in a macro that evaluates to nothing
>> when CONFIG_DEBUG_LOCK_ALLOC is not defined. Change to use the correct
>> variable that does exist.
>>
>> ---
>>
>> reported by kbuild test robot on on robh/for-next
>> https://lkml.org/lkml/2017/4/29/134
>
> That's a bit misleading because I've not applied the offending patch.
> Please squash this.
>
> Rob
Does "squash this" mean to redo the original path to include this fix?
Thanks,
Frank
Powered by blists - more mailing lists