From: Sean Christopherson <seanjc@google.com>
To: seanjc@google.com
Cc: Binbin Wu <binbin.wu@linux.intel.com>,
Anish Moorthy <amoorthy@google.com>,
Zeng Guang <guang.zeng@intel.com>,
John Allen <john.allen@amd.com>,
Yang Weijiang <weijiang.yang@intel.com>,
kvm@vger.kernel.org
Subject: KVM x86 reviews status for 6.5
Date: Wed, 7 Jun 2023 16:24:11 -0700 [thread overview]
Message-ID: <ZIERmyVzarYcsWT7@google.com> (raw)
Folks on the Cc list, you've posted series series that I haven't reviewed recently,
and may or may not review before the 6.5 merge window, but I pinky swear your
series are on my todo list. This past month was hectic for non-work reasons and
I got behind on reviews (obviously). I deliberately prioritized patches/series
that I thought were likely to be ready for 6.5, which meant that your series got
ignored for a while. Sorry :-(
I have some vacations/holidays coming up, including the rest of this week, and so
reviews will likely be slower than you want for the next 3-4 weeks. My goal is
to at least do one pass through all of your series before the end of June, though
I've no idea if that's realistic. Again, sorry for the delays.
reply other threads:[~2023-06-07 23:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ZIERmyVzarYcsWT7@google.com \
--to=seanjc@google.com \
--cc=amoorthy@google.com \
--cc=binbin.wu@linux.intel.com \
--cc=guang.zeng@intel.com \
--cc=john.allen@amd.com \
--cc=kvm@vger.kernel.org \
--cc=weijiang.yang@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.