[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.9999.1912050900030.218941@viisi.sifive.com>
Date: Thu, 5 Dec 2019 09:01:02 -0800 (PST)
From: Paul Walmsley <paul.walmsley@...ive.com>
To: Anup Patel <anup@...infault.org>
cc: Anup Patel <Anup.Patel@....com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
Atish Patra <Atish.Patra@....com>,
Alistair Francis <Alistair.Francis@....com>,
Christoph Hellwig <hch@....de>,
"linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] RISC-V: Add debug defconfigs
On Thu, 5 Dec 2019, Anup Patel wrote:
> I understand that you need DEBUG options for SiFive internal
> use
[ ... ]
> This is the right time to introduce debug defconfigs so that you can
> use it for your SiFive internal use
[ ... ]
> and you can find an alternative way to enable DEBUG options for SiFive
> internal use.
What leads you to conclude that this was done for SiFive internal use?
- Paul
Powered by blists - more mailing lists