[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.9999.1910222348260.12442@viisi.sifive.com>
Date: Tue, 22 Oct 2019 23:49:17 -0700 (PDT)
From: Paul Walmsley <paul.walmsley@...ive.com>
To: Anup Patel <anup@...infault.org>
cc: Alistair Francis <Alistair.Francis@....com>,
Anup Patel <Anup.Patel@....com>,
"linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>,
Atish Patra <Atish.Patra@....com>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"rkir@...gle.com" <rkir@...gle.com>,
"hch@...radead.org" <hch@...radead.org>,
"aou@...s.berkeley.edu" <aou@...s.berkeley.edu>,
"palmer@...ive.com" <palmer@...ive.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 2/2] RISC-V: defconfig: Enable Goldfish RTC driver
On Wed, 23 Oct 2019, Anup Patel wrote:
> On Wed, Oct 23, 2019 at 11:30 AM Paul Walmsley <paul.walmsley@...ive.com> wrote:
>
> > Is drivers/platform/goldfish/goldfish_pipe.c required for the Goldfish RTC
> > driver or not?
>
> No, it's not required.
>
> > If not, then the first patch that was sent isn't the right fix. It would
> > be better to remove the Kbuild dependency between the code in
> > drivers/platform/goldfish and the Goldfish RTC.
>
> The common GOLDFISH kconfig option is there to specify the
> common expectations of all GOLDFISH drivers from Linux ARCH
> support.
OK, then in that case the Goldfish RTC sounds reasonable to me.
- Paul
Powered by blists - more mailing lists