From: Sean Christopherson <seanjc@google.com>
To: Ben Gardon <bgardon@google.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>, Peter Xu <peterx@redhat.com>,
David Matlack <dmatlack@google.com>,
Vipin Sharma <vipinsh@google.com>
Subject: Re: [RFC 1/2] selftests: KVM: Move dirty logging functions to memstress.(c|h)
Date: Thu, 19 Jan 2023 20:39:19 +0000 [thread overview]
Message-ID: <Y8mqd7HUzXDnhXLV@google.com> (raw)
In-Reply-To: <20230119200553.3922206-1-bgardon@google.com>
Please provide cover letters for multi-patch series, regardless of how trivial
the series is.
This series especially needs a cover explaining why it's tagged "RFC".
next prev parent reply other threads:[~2023-01-19 20:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 20:05 [RFC 1/2] selftests: KVM: Move dirty logging functions to memstress.(c|h) Ben Gardon
2023-01-19 20:05 ` [RFC 2/2] selftests: KVM: Add page splitting test Ben Gardon
2023-01-19 20:39 ` Sean Christopherson [this message]
2023-01-19 20:47 ` [RFC 1/2] selftests: KVM: Move dirty logging functions to memstress.(c|h) Ben Gardon
2023-01-19 20:53 ` Sean Christopherson
2023-01-19 21:27 ` Ben Gardon
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=Y8mqd7HUzXDnhXLV@google.com \
--to=seanjc@google.com \
--cc=bgardon@google.com \
--cc=dmatlack@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=vipinsh@google.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.