[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqKMB4exBFTDNFAio87JeOF0sXjMBkueizgfoiG38Mb_8A@mail.gmail.com>
Date: Mon, 1 May 2017 15:13:14 -0500
From: Rob Herring <robh+dt@...nel.org>
To: Frank Rowand <frank.rowand@...y.com>
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>
Subject: Re: [PATCH] of: undeclared variable when CONFIG_DEBUG_LOCK_ALLOC
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
Powered by blists - more mailing lists