mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	Sean Christopherson <seanjc@google.com>
Subject: Re: [GIT PULL] First batch of KVM changes for Linux 6.1
Date: Thu, 6 Oct 2022 02:02:32 +0200	[thread overview]
Message-ID: <8602ab30-27e4-ae2d-d502-0f025c725801@redhat.com> (raw)
In-Reply-To: <20220930190836.116605-1-pbonzini@redhat.com>

On 9/30/22 21:08, Paolo Bonzini wrote:
> The first batch of KVM patches, mostly covering x86, which I
> am sending out early due to me travelling next week.  There is a
> lone mm patch for which Andrew gave an informal ack at
> https://lore.kernel.org/linux-mm/20220817102500.440c6d0a3fce296fdf91bea6@linux-foundation.org.
> 
> I will send the bulk of ARM work, as well as other
> architectures, at the end of next week.

Linus,

this hasn't been pulled yet, and I suspect that's because most patches 
have not been in linux-next for most of the 6.0-rc period, which earned 
me a place in the well-known shitlist.

So, what happened is that this is the first release with KVM/x86 
submaintainers.  I have noticed now that we have never asked for Sean's 
tree to be added to linux-next.  Sorry about that.

It is now "the end of next week", but I will wait a few more days for 
you to process this pull request, and then send the ARM/RISC-V parts.

Thanks,

Paolo


  reply	other threads:[~2022-10-06  0:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30 19:08 Paolo Bonzini
2022-10-06  0:02 ` Paolo Bonzini [this message]
2022-10-09 21:17 ` pr-tracker-bot

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=8602ab30-27e4-ae2d-d502-0f025c725801@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seanjc@google.com \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®