[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191001101016.GB23507@infradead.org>
Date: Tue, 1 Oct 2019 03:10:16 -0700
From: "hch@...radead.org" <hch@...radead.org>
To: Atish Patra <Atish.Patra@....com>
Cc: "hch@...radead.org" <hch@...radead.org>,
"anup@...infault.org" <anup@...infault.org>,
"paul.walmsley@...ive.com" <paul.walmsley@...ive.com>,
"linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"palmer@...ive.com" <palmer@...ive.com>,
"aou@...s.berkeley.edu" <aou@...s.berkeley.edu>,
"johan@...nel.org" <johan@...nel.org>
Subject: Re: [v6 PATCH] RISC-V: Remove unsupported isa string info print
On Tue, Oct 01, 2019 at 08:22:37AM +0000, Atish Patra wrote:
> riscv_of_processor_hartid() or seems to be a better candidate. We
> already check if "rv" is present in isa string or not. I will extend
> that to check for rv64i or rv32i. Is that okay ?
I'd rather lift the checks out of that into a function that is called
exactly once per hart on boot (and future cpu hotplug).
Powered by blists - more mailing lists