From: Sean Christopherson <seanjc@google.com>
To: rdunlap@infradead.org, Jiaming Zhang <r772577952@gmail.com>
Cc: corbet@lwn.net, kvm@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, pbonzini@redhat.com
Subject: Re: [PATCH v2] Documentation: KVM: Add reference specs for PIT and LAPIC ioctls
Date: Tue, 16 Sep 2025 13:02:38 -0700 [thread overview]
Message-ID: <aMnCXgLWN4xX6hjM@google.com> (raw)
In-Reply-To: <175798208800.624836.165612810420047605.b4-ty@google.com>
On Mon, Sep 15, 2025, Sean Christopherson wrote:
> On Sat, 06 Sep 2025 01:47:36 +0800, Jiaming Zhang wrote:
> > Thanks for your feedback! I have fixed the grammar and put the full URL on a single line.
> >
> > Please let me know if any other changes are needed.
> >
> > Thanks,
> > Jiaming Zhang
> >
> > [...]
>
> Applied to kvm-x86 misc, but only for the PIT documentation update.
...
> [1/1] Documentation: KVM: Add reference specs for PIT and LAPIC ioctls
> https://github.com/kvm-x86/linux/commit/3f0bb03b9db7
I force pushed to fixup an unrelated commit, new hash:
https://github.com/kvm-x86/linux/commit/5b5133e6a55b
prev parent reply other threads:[~2025-09-16 20:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 5:39 [Discussion] Undocumented behavior of KVM_SET_PIT2 with count=0 Jiaming Zhang
2025-08-26 17:50 ` Sean Christopherson
2025-08-27 2:31 ` Jiaming Zhang
2025-09-05 7:51 ` [PATCH] Documentation: KVM: Add reference specs for PIT and LAPIC ioctls Jiaming Zhang
2025-09-05 16:51 ` Randy Dunlap
2025-09-05 17:47 ` [PATCH v2] " Jiaming Zhang
2025-09-05 19:17 ` Randy Dunlap
2025-09-16 0:25 ` Sean Christopherson
2025-09-16 20:02 ` Sean Christopherson [this message]
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=aMnCXgLWN4xX6hjM@google.com \
--to=seanjc@google.com \
--cc=corbet@lwn.net \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=r772577952@gmail.com \
--cc=rdunlap@infradead.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