[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <mhng-aa617456-63d1-4275-8032-126a6b21305c@palmer-si-x1c4>
Date: Thu, 06 Sep 2018 02:45:06 -0700 (PDT)
From: Palmer Dabbelt <palmer@...ive.com>
To: atish.patra@....com
CC: Christoph Hellwig <hch@...radead.org>,
linux-riscv@...ts.infradead.org, daniel.lezcano@...aro.org,
jason@...edaemon.net, ard.biesheuvel@...aro.org,
marc.zyngier@....com, catalin.marinas@....com,
dmitriy@...-tech.org, jeremy.linton@....com,
linux-kernel@...r.kernel.org, aou@...s.berkeley.edu,
Greg KH <gregkh@...uxfoundation.org>, tglx@...utronix.de
Subject: Re: [PATCH 5/8] RISC-V: Rename im_okay_therefore_i_am to found_boot_cpu
On Thu, 30 Aug 2018 09:11:11 PDT (-0700), atish.patra@....com wrote:
> On 8/30/18 7:41 AM, Christoph Hellwig wrote:
>>> struct device_node *dn = NULL;
>>> - int hart, im_okay_therefore_i_am = 0;
>>> + int hart, found_boot_cpu = 0;
>>
>> If you rename this anyway please switch to use a bool.
>>
>
> I can address the comment on this patch and fold it in my series to
> avoid unnecessary conflict.
>
> @Palmer: You can drop this patch.
Thanks!
Powered by blists - more mailing lists