[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <mhng-d0cd3a60-098d-40dd-912c-f0cb77d54ae7@palmer-si-x1c4>
Date: Mon, 11 Feb 2019 11:59:40 -0800 (PST)
From: Palmer Dabbelt <palmer@...ive.com>
To: johan@...nel.org
CC: aou@...s.berkeley.edu, schwab@...e.de, atish.patra@....com,
anup@...infault.org, linux-riscv@...ts.infradead.org,
linux-kernel@...r.kernel.org, johan@...nel.org
Subject: Re: [PATCH 0/5] riscv: minor fixes and cleanups
On Mon, 11 Feb 2019 01:34:06 PST (-0800), johan@...nel.org wrote:
> On Fri, Jan 18, 2019 at 03:03:03PM +0100, Johan Hovold wrote:
>> This series fix up some minor issues found through inspection.
>>
>> Note that the fourth patch changes which cpu (hart) devicetree nodes
>> are enabled by following the Linux convention of considering nodes
>> without a status property as enabled.
>>
>> These patches are against the riscv-next (and fixes) branch with Andreas
>> node-reference fix applied:
>>
>> https://lore.kernel.org/lkml/mvm8szwwo1o.fsf@suse.de/
>>
>> and have been tested using QEMU.
>
>> Johan Hovold (5):
>> riscv: add missing newlines to printk messages
>> riscv: use pr_info and friends
>> riscv: fix riscv_of_processor_hartid() comment
>> riscv: treat cpu devicetree nodes without status as enabled
>> riscv: use for_each_of_cpu_node iterator
>
> Are these still in your queue, Palmer?
>
> Note that the node-reference dependency mentioned above is now in
> Linus's tree.
They're still in my queue. With any luck I'll have time tonight to go through
by Linux patch review backlog.
Powered by blists - more mailing lists