mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Sean Christopherson <seanjc@google.com>
Subject: [GIT PULL] KVM: x86 pull requests for 6.7
Date: Fri, 27 Oct 2023 13:49:24 -0700	[thread overview]
Message-ID: <20231027204933.3651381-1-seanjc@google.com> (raw)

I know you said a cover letter isn't necessary, but sending everything all at
once helps me keep track of things, and git send-email replying to whatever
random pull request happens to come first alphabetically bugs me.

  [GIT PULL] KVM: x86: APIC changes for 6.7
  [GIT PULL] KVM: x86: Documentation updates for 6.7
  [GIT PULL] KVM: x86: Misc changes for 6.7
  [GIT PULL] KVM: x86: PMU change for 6.7
  [GIT PULL] KVM: x86: SVM changes for 6.7
  [GIT PULL] KVM: x86: Xen changes for 6.7

Don't get used to the low volume, the next few cycles are likely to be chonkers.
But, I have started using dedicated topic branches for larger series, e.g. for
guest_memfd and LAM support, and I'll send pull requests for such branches much
earlier in the cycle.  So, in theory, the size of the pull requests that come in
just before the merge window will still be relatively small.

Speaking of pull requests coming in just before the merge window, I meant to get
these sent out earlier this week, but guest_memfd happened.  At least it looks
like I'll still beat Oliver, which is all that matters :-)

             reply	other threads:[~2023-10-27 20:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-27 20:49 Sean Christopherson [this message]
2023-10-27 20:49 ` [GIT PULL] KVM: x86: APIC changes " Sean Christopherson
2023-10-31 14:15   ` Paolo Bonzini
2023-10-27 20:49 ` [GIT PULL] KVM: x86: Documentation updates " Sean Christopherson
2023-10-31 14:14   ` Paolo Bonzini
2023-10-27 20:49 ` [GIT PULL] KVM: x86: Misc changes " Sean Christopherson
2023-10-31 14:21   ` Paolo Bonzini
2023-10-27 20:49 ` [GIT PULL] KVM: x86: MMU " Sean Christopherson
2023-10-31 14:20   ` Paolo Bonzini
2023-10-27 20:49 ` [GIT PULL] KVM: x86: PMU change " Sean Christopherson
2023-10-27 20:49 ` [GIT PULL] KVM: x86: SVM changes " Sean Christopherson
2023-10-31 14:55   ` Paolo Bonzini
2023-10-27 20:49 ` [GIT PULL] KVM: x86: Xen " Sean Christopherson
2023-10-31 14:22   ` Paolo Bonzini

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=20231027204933.3651381-1-seanjc@google.com \
    --to=seanjc@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®