public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list@gmail.com>
To: "Rowand, Frank" <Frank.Rowand@sony.com>,
	Rob Herring <robh+dt@kernel.org>
Cc: Stephen Boyd <stephen.boyd@linaro.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] of: undeclared variable when CONFIG_DEBUG_LOCK_ALLOC
Date: Mon, 1 May 2017 15:23:22 -0700	[thread overview]
Message-ID: <5907B55A.1080803@gmail.com> (raw)
In-Reply-To: <ED290C750E1B324E972B0017C9D4BAB01FDD5370@USCULXMSG01.am.sony.com>

On 05/01/17 14:20, Rowand, Frank wrote:
> On Monday, May 01, 2017 1:13 PM, Rob Herring [mailto:robh+dt@kernel.org]  wrote:
>>
>> On Sun, Apr 30, 2017 at 3:00 PM, Frank Rowand <frank.rowand@sony.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?

                                               ^^^^  patch

> 
> Thanks,
> 
> Frank
> 

  reply	other threads:[~2017-05-01 22:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1493582403-12291-1-git-send-email-frank.rowand@sony.com>
2017-05-01 20:13 ` [PATCH] of: undeclared variable when CONFIG_DEBUG_LOCK_ALLOC Rob Herring
2017-05-01 21:20   ` Rowand, Frank
2017-05-01 22:23     ` Frank Rowand [this message]
2017-04-30 20:45 frowand.list

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5907B55A.1080803@gmail.com \
    --to=frowand.list@gmail.com \
    --cc=Frank.Rowand@sony.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=stephen.boyd@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox