mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: 陈华才 <chenhc@lemote.com>, "Roman Kiryanov" <rkir@google.com>,
	"Huacai Chen" <chenhuacai@gmail.com>,
	"Paul Walmsley" <paul.walmsley@sifive.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"Lingfeng Yang" <lfy@google.com>, "Rob Herring" <robh@kernel.org>,
	anup.patel@wdc.com, Alistair.Francis@wdc.com,
	qemu-riscv@nongnu.org
Subject: Re: Re: [PATCH] drivers: rtc: retire RTC_DRV_GOLDFISH
Date: Sat, 14 Nov 2020 11:23:20 +0100	[thread overview]
Message-ID: <X6+wGMUCCpu2liYR@kroah.com> (raw)
In-Reply-To: <d1d47715-482c-f598-a958-499d9fde21e0@flygoat.com>

On Sat, Nov 14, 2020 at 05:47:47PM +0800, Jiaxun Yang wrote:
> 
> 
> 在 2020/11/14 下午4:15, Greg KH 写道:
> 
> + qemu-riscv list and QEMU device maintainers of goldfish_rtc
> 
> > On Sat, Nov 14, 2020 at 04:06:24PM +0800, 陈华才 wrote:
> > > Hi, All,
> > > 
> > > Goldfish RTC works well on MIPS, and QEMU RISC-V emulator use Goldfish
> > > as well, so I think  we should keep it in kernel.
> > But does anyone actually use it for anything?  Having something in qemu
> > is nice, but not required if it doesn't provide something that is
> > already there for other virtual devices, right?
> 
> Hi all,
> 
> Both QEMU MIPS loongson3-virt and riscv virt machine are using goldfish_rtc
> as sole RTC
> device, it have been hardcoded in QEMU for a long while and sudden drop in
> kernel would
> break these machines.
> RTC is essential for virt machines to keep time synchronized with host.
> 
> Given that it is the simplest RTC implementation for now, it won't give us
> much maintenance
> overhead.
> 
> Thus I do think it shouldn't be retired as for now. If nobody comes in I'd
> also willing to maintain
> it.

Ok, can someone submit a patch to update the MAINTAINERS file for this
so we know who to route issues to over time?

thanks,

greg k-h

  reply	other threads:[~2020-11-14 10:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13 20:52 rkir
2020-11-13 21:07 ` Rob Herring
2020-11-13 21:13   ` Roman Kiryanov
2020-11-13 21:17     ` Rob Herring
2020-11-13 22:02       ` Roman Kiryanov
2020-11-13 23:36         ` Roman Kiryanov
2020-11-13 23:44           ` Greg KH
     [not found]             ` <tencent_3801BEAE39670E174105E007@qq.com>
2020-11-14  8:15               ` Greg KH
2020-11-14  9:47                 ` Jiaxun Yang
2020-11-14 10:23                   ` Greg KH [this message]
2020-11-14 22:03                     ` Roman Kiryanov
2020-12-08 22:28                   ` Roman Kiryanov
2020-12-09  4:03                     ` Jiaxun Yang
2020-11-14  8:15               ` Greg KH
2020-11-14  8:59                 ` Huacai Chen
2020-11-14 22:01               ` Roman Kiryanov
2020-11-15  6:43                 ` Huacai Chen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=X6+wGMUCCpu2liYR@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Alistair.Francis@wdc.com \
    --cc=anup.patel@wdc.com \
    --cc=chenhc@lemote.com \
    --cc=chenhuacai@gmail.com \
    --cc=jiaxun.yang@flygoat.com \
    --cc=lfy@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.walmsley@sifive.com \
    --cc=qemu-riscv@nongnu.org \
    --cc=rkir@google.com \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome