public inbox for linux-kernel@vger.kernel.org
 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: One lone common change for 6.18
Date: Fri, 26 Sep 2025 23:09:02 -0700	[thread overview]
Message-ID: <20250927060910.2933942-3-seanjc@google.com> (raw)
In-Reply-To: <20250927060910.2933942-1-seanjc@google.com>

Tag says it all...

The following changes since commit c17b750b3ad9f45f2b6f7e6f7f4679844244f0b9:

  Linux 6.17-rc2 (2025-08-17 15:22:10 -0700)

are available in the Git repository at:

  https://github.com/kvm-x86/linux.git tags/kvm-x86-generic-6.18

for you to fetch changes up to cf6a8401b6a12c3bdd54c7414af28625ec6450da:

  KVM: remove redundant __GFP_NOWARN (2025-08-19 11:51:13 -0700)

----------------------------------------------------------------
KVM common changes for 6.18

Remove a redundant __GFP_NOWARN from kvm_setup_async_pf() as __GFP_NOWARN is
now included in GFP_NOWAIT.

----------------------------------------------------------------
Qianfeng Rong (1):
      KVM: remove redundant __GFP_NOWARN

 virt/kvm/async_pf.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

  parent reply	other threads:[~2025-09-27  6:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-27  6:09 [GIT PULL] KVM: x86 pull requests 6.18 Sean Christopherson
2025-09-27  6:09 ` [GIT PULL] x86/kvm: Guest side changes for 6.18 Sean Christopherson
2025-09-30 17:28   ` Paolo Bonzini
2025-09-27  6:09 ` Sean Christopherson [this message]
2025-09-30 17:28   ` [GIT PULL] KVM: One lone common change " Paolo Bonzini
2025-09-27  6:09 ` [GIT PULL] KVM: x86: MMU changes " Sean Christopherson
2025-09-30 17:33   ` Paolo Bonzini
2025-09-27  6:09 ` [GIT PULL] KVM: Selftests " Sean Christopherson
2025-09-30 17:24   ` Paolo Bonzini
2025-09-27  6:09 ` [GIT PULL] KVM: x86: VMX " Sean Christopherson
2025-09-30 17:33   ` Paolo Bonzini
2025-09-27  6:09 ` [GIT PULL] KVM: x86: SVM " Sean Christopherson
2025-09-30 17:35   ` Paolo Bonzini
2025-09-27  6:09 ` [GIT PULL] KVM: x86: SNP CipherTextHiding " Sean Christopherson
2025-09-30 17:35   ` Paolo Bonzini
2025-09-27  6:09 ` [GIT PULL] KVM: x86: Misc changes " Sean Christopherson
2025-09-30 18:06   ` Paolo Bonzini
2025-09-27  6:09 ` [GIT PULL] KVM: x86: CET virtualization " Sean Christopherson
2025-09-27  6:09 ` [GIT PULL] KVM: Symbol export restrictions " Sean Christopherson
2025-09-30 17:41   ` Paolo Bonzini
2025-09-30 18:10 ` [GIT PULL] KVM: x86 pull requests 6.18 Paolo Bonzini
2025-09-30 19:16   ` Sean Christopherson

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=20250927060910.2933942-3-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