On Thu, 2025-01-09 at 07:52 -0500, Stefan Hajnoczi wrote: > On Wed, 8 Jan 2025 at 06:11, David Woodhouse <dw...@infradead.org> > wrote: > > > > From: David Woodhouse <d...@amazon.co.uk> > > > > The following changes since commit > > 6528013b5f5ba6bb3934b7f5fe57a3110680530f: > > > > Merge tag 'qga-pull-2025-01-06' of > > https://github.com/kostyanf14/qemu into staging (2025-01-06 > > 09:39:02 -0500) > > > > are available in the Git repository at: > > > > git://git.infradead.org/users/dwmw2/qemu.git tags/pull-vmclock- > > 20250108 > > > > for you to fetch changes up to > > 6502ea82b26dc28c83fbc9c766af7a408a8ca827: > > > > hw/acpi: Add vmclock device (2025-01-07 16:22:04 +0000) > > > > ---------------------------------------------------------------- > > Add vmclock device > > > > ---------------------------------------------------------------- > > David Woodhouse (1): > > hw/acpi: Add vmclock device > > > > hw/acpi/Kconfig | 5 + > > hw/acpi/meson.build | 1 + > > hw/acpi/vmclock.c | 179 > > ++++++++++++++++++++++++++ > > hw/i386/Kconfig | 1 + > > hw/i386/acpi-build.c | 10 +- > > include/hw/acpi/vmclock.h | 34 +++++ > > include/standard-headers/linux/vmclock-abi.h | 182 > > +++++++++++++++++++++++++++ > > scripts/update-linux-headers.sh | 1 + > > 8 files changed, 412 insertions(+), 1 deletion(-) > > create mode 100644 hw/acpi/vmclock.c > > create mode 100644 include/hw/acpi/vmclock.h > > create mode 100644 include/standard-headers/linux/vmclock-abi.h > > On IRC you mentioned that you'd like me to pick up this pull request. > If the ACPI subsystem maintainers don't want to take this through > their tree then let's set up pull request handling for vmclock: > > 1. Add a MAINTAINERS file entry for vmclock covering the new files > (e.g. hw/acpi/vmclock.c) with yourself as maintainer.
Looks like Michael has taken it now; thanks. > 2. Send pull requests with a GPG-signed tag (git tag --sign) and > ensure that the repo URL in the email is https:// (the tooling rejects > unencrypted http:// and git:// repo URLs). You mean *or* rather than *and* in that sentence, right? Because if it's GPG-signed, then I can send it to you over carrier pigeon and you can validate it; the transport is irrelevant. If you really did mean 'and'... is this a new bug in the tooling? Last time I used Peter's make-pullreq script, it worked fine¹. Obviously it doesn't matter for *this* one now Michael has picked it up, but I sent another pull request today with some Xen emulation fixes². ¹ https://lore.kernel.org/all/cafeaca9sjovbldv1nsundgps9hx1xyn7szbetq-crtz84vo...@mail.gmail.com/ ² https://lore.kernel.org/qemu-devel/20250109104837.2532259-1-dw...@infradead.org/
smime.p7s
Description: S/MIME cryptographic signature
