U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hung-Chun Tseng <alan.tseng.cs@gmail.com>
To: Kuan-Wei Chiu <visitorckw@gmail.com>
Cc: Bin Meng <bmeng.cn@gmail.com>, Tom Rini <trini@konsulko.com>,
	Simon Glass <sjg@chromium.org>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>,
	u-boot@lists.u-boot-project.org
Subject: Re: [PATCH v2 1/3] virtio: rtc: Add virtio RTC driver
Date: Sat, 17 Oct 2026 00:41:31 +0800	[thread overview]
Message-ID: <20261016164131.402292-1-alan.tseng.cs@gmail.com> (raw)
In-Reply-To: <as_b-1hWbg03DGOJ@google.com>

Hi Kuan-Wei,

On Thu, Oct 15, 2026 at 03:46:03AM +0800, Kuan-Wei Chiu wrote:
> Actually, when I sent out the qemu virtio-rtc code, I also had a local
> dirty version of the virtio-rtc u-boot driver, but it has been sitting
> on my TODO list. I might take a closer look at this patch in a day or
> two.

Thanks for taking a look, and for the QEMU device that made this easy
to test. If your local version handles something mine doesn't, I'm
happy to fold it in.

> I would suggest leaving more time between sending out new patch
> versions to give people a chance to review and reply, which helps avoid
> spamming the list with rapid revisions.

Understood, sorry about that. I'll hold v3 until you and others have
had time to go through v2.

> IIRC, when I sent out the virtio-9p driver for review, Simon made the
> same suggestion to add a timeout mechanism to the loop here to prevent
> potential hangs.

Good point. For v3 I have the loop bounded with get_timer(), giving up
with -ETIMEDOUT after one second, as virtio_9p does.

For your comments on 2/3, v3 also turns the device types into a
bulleted list and retitles the patch to "doc: virtio: List the
supported device types".

Thanks,
Hung-Chun

  reply	other threads:[~2026-10-16 16:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14 19:06 [PATCH v2 0/3] virtio: Add a virtio RTC driver Hung-Chun Tseng
2026-10-14 19:06 ` [PATCH v2 1/3] virtio: rtc: Add " Hung-Chun Tseng
2026-10-14 19:46   ` Kuan-Wei Chiu
2026-10-16 16:41     ` Hung-Chun Tseng [this message]
2026-10-16 21:47   ` Simon Glass
2026-10-17 18:28   ` Kuan-Wei Chiu
2026-10-14 19:06 ` [PATCH v2 2/3] doc: virtio: Mention the RTC device Hung-Chun Tseng
2026-10-14 19:30   ` Kuan-Wei Chiu
2026-10-16 21:47   ` Simon Glass
2026-10-14 19:06 ` [PATCH v2 3/3] MAINTAINERS: Add entry for virtio RTC Hung-Chun Tseng
2026-10-16 21:47   ` Simon Glass

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=20261016164131.402292-1-alan.tseng.cs@gmail.com \
    --to=alan.tseng.cs@gmail.com \
    --cc=bmeng.cn@gmail.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.u-boot-project.org \
    --cc=visitorckw@gmail.com \
    --cc=xypron.glpk@gmx.de \
    /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