From: Bagas Sanjaya <bagasdotme@gmail•com>
To: Paolo Bonzini <pbonzini@redhat•com>
Cc: linux-doc@vger•kernel.org, Jonathan Corbet <corbet@lwn•net>,
David Matlack <dmatlack@google•com>,
Ben Gardon <bgardon@google•com>, Peter Xu <peterx@redhat•com>,
kvm@vger•kernel.org, linux-next@vger•kernel.org,
linux-kernel@vger•kernel.org
Subject: Re: [PATCH next 0/2] Documentation: KVM: KVM_CAP_VM_DISABLE_NX_HUGE_PAGES documentation fixes
Date: Thu, 11 Aug 2022 20:30:36 +0700 [thread overview]
Message-ID: <1db2a0cd-bef1-213c-a411-3d39d378743a@gmail.com> (raw)
In-Reply-To: <20220811063601.195105-1-pbonzini@redhat.com>
On 8/11/22 13:36, Paolo Bonzini wrote:
> Queued, thanks.
>
> Paolo
>
>
Thanks for picking this up. However, Stephen noted that the issue is
already showed up on mainline [1]. Maybe this series should be queued
for 6.0 release (as -rc fixes), right?
[1]: https://lore.kernel.org/linux-next/20220809164147.131f87d0@canb.auug.org.au/
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-08-11 13:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 9:51 [PATCH next 0/2] Documentation: KVM: KVM_CAP_VM_DISABLE_NX_HUGE_PAGES documentation fixes Bagas Sanjaya
2022-06-27 9:51 ` [PATCH next 1/2] Documentation: KVM: extend KVM_CAP_VM_DISABLE_NX_HUGE_PAGES heading underline Bagas Sanjaya
2022-06-27 9:51 ` [PATCH next 2/2] KVM: x86/MMU: properly format KVM_CAP_VM_DISABLE_NX_HUGE_PAGES capability table Bagas Sanjaya
2022-08-11 6:36 ` [PATCH next 0/2] Documentation: KVM: KVM_CAP_VM_DISABLE_NX_HUGE_PAGES documentation fixes Paolo Bonzini
2022-08-11 13:30 ` Bagas Sanjaya [this message]
2022-08-12 7:40 ` Paolo Bonzini
2022-08-13 7:31 ` Bagas Sanjaya
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=1db2a0cd-bef1-213c-a411-3d39d378743a@gmail.com \
--to=bagasdotme@gmail$(echo .)com \
--cc=bgardon@google$(echo .)com \
--cc=corbet@lwn$(echo .)net \
--cc=dmatlack@google$(echo .)com \
--cc=kvm@vger$(echo .)kernel.org \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=pbonzini@redhat$(echo .)com \
--cc=peterx@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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