From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Aaron Lewis <aaronlewis@google.com>
Cc: pbonzini@redhat.com, rkrcmar@redhat.com, jmattson@google.com,
marcorr@google.com, kvm@vger.kernel.org,
Peter Shier <pshier@google.com>
Subject: Re: [PATCH] tests: kvm: Add tests to .gitignore
Date: Fri, 3 May 2019 09:30:57 -0700 [thread overview]
Message-ID: <20190503163057.GA32628@linux.intel.com> (raw)
In-Reply-To: <20190502183150.259633-1-aaronlewis@google.com>
On Thu, May 02, 2019 at 11:31:50AM -0700, Aaron Lewis wrote:
> Signed-off-by: Aaron Lewis <aaronlewis@google.com>
> Reviewed-by: Peter Shier <pshier@google.com>
> Reviewed-by: Jim Mattson <jmattson@google.com>
> ---
> 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
Super nit: would you want to organize these alphabetically? Only the last
two entries (x86_64/state_test and dirty_log_test) would need to be moved.
Wish we didn't have to play whack-a-mole with ignoring tests, but a quick
glance at the selftest build system doesn't reveal an easy way to provide
and ignore an output directory :(
Reviewed-by: Sean Christopherson <sean.j.christopherson@intel.com>
next prev parent reply other threads:[~2019-05-03 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 18:31 [PATCH] tests: kvm: Add tests to .gitignore Aaron Lewis
2019-05-03 16:30 ` Sean Christopherson [this message]
2019-05-08 12:01 ` Paolo Bonzini
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=20190503163057.GA32628@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=aaronlewis@google.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=marcorr@google.com \
--cc=pbonzini@redhat.com \
--cc=pshier@google.com \
--cc=rkrcmar@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 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.