From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Kelsey Skunberg <skunberg.kelsey@gmail.com>
Cc: shuah@kernel.org, pbonzini@redhat.com, rkrcmar@redhat.com,
linux-kselftest@vger.kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH v2] selftests: kvm: Add files generated when compiled to .gitignore
Date: Mon, 13 May 2019 07:03:05 -0700 [thread overview]
Message-ID: <20190513140305.GA28561@linux.intel.com> (raw)
In-Reply-To: <20190512044434.32627-1-skunberg.kelsey@gmail.com>
On Sat, May 11, 2019 at 10:44:34PM -0600, Kelsey Skunberg wrote:
> The following files are generated in /selftests/kvm/ after compiling and
> should be added to /selftests/kvm/.gitignore:
>
> - /x86_64/hyperv_cpuid
> - /x86_64/smm_test
> - /clear_dirty_log_test
>
> Signed-off-by: Kelsey Skunberg <skunberg.kelsey@gmail.com>
> ---
An equivalent patch has already been queued.
https://patchwork.kernel.org/patch/10931115/
> Changes since v1:
> - Included /clear_dirty_log_test to .gitignore
> - Updated commit log to reflect file added
>
> tools/testing/selftests/kvm/.gitignore | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/tools/testing/selftests/kvm/.gitignore b/tools/testing/selftests/kvm/.gitignore
> index 2689d1ea6d7a..391a19231618 100644
> --- a/tools/testing/selftests/kvm/.gitignore
> +++ b/tools/testing/selftests/kvm/.gitignore
> @@ -6,4 +6,7 @@
> /x86_64/vmx_close_while_nested_test
> /x86_64/vmx_tsc_adjust_test
> /x86_64/state_test
> +/x86_64/hyperv_cpuid
> +/x86_64/smm_test
> +/clear_dirty_log_test
> /dirty_log_test
> --
> 2.20.1
>
prev parent reply other threads:[~2019-05-13 14:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5d60e7126803e9a11b51618e65966ba047eff7df>
2019-05-12 4:44 ` [PATCH v2] selftests: kvm: Add files generated when compiled to .gitignore Kelsey Skunberg
2019-05-13 14:03 ` Sean Christopherson [this message]
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=20190513140305.GA28561@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=skunberg.kelsey@gmail.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