From: Anders Roxell <anders.roxell@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>, Shuah Khan <shuah@kernel.org>
Cc: "open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] selftests/kvm: add missing executables to .gitignore
Date: Thu, 31 Jan 2019 20:09:01 +0100 [thread overview]
Message-ID: <CADYN=9LXeLv=cxJSJmWLybHqDhDx=nG3arfc32cjwB42iSb7vA@mail.gmail.com> (raw)
In-Reply-To: <20190108092654.13113-1-anders.roxell@linaro.org>
On Tue, 8 Jan 2019 at 10:27, Anders Roxell <anders.roxell@linaro.org> wrote:
>
> Fixes: 2a31b9db1535 ("kvm: introduce manual dirty log reprotect")
> Fixes: 7edcb7343327 ("KVM: selftests: Add hyperv_cpuid test")
> Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
> ---
> tools/testing/selftests/kvm/.gitignore | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/tools/testing/selftests/kvm/.gitignore b/tools/testing/selftests/kvm/.gitignore
> index 6210ba41c29e..51ffd8a8bc38 100644
> --- a/tools/testing/selftests/kvm/.gitignore
> +++ b/tools/testing/selftests/kvm/.gitignore
> @@ -1,8 +1,10 @@
> /x86_64/cr4_cpuid_sync_test
> /x86_64/evmcs_test
> +/x86_64/hyperv_cpuid
> /x86_64/platform_info_test
> /x86_64/set_sregs_test
> /x86_64/sync_regs_test
> /x86_64/vmx_tsc_adjust_test
> /x86_64/state_test
> +/clear_dirty_log_test
> /dirty_log_test
> --
> 2.20.1
>
Does this make sense or should I redo it?
Cheers,
Anders
next prev parent reply other threads:[~2019-01-31 19:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 9:26 [PATCH] selftests/kvm: add missing executables to .gitignore Anders Roxell
2019-01-31 19:09 ` Anders Roxell [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-10-19 14:38 Anders Roxell
2018-10-19 16:15 ` 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='CADYN=9LXeLv=cxJSJmWLybHqDhDx=nG3arfc32cjwB42iSb7vA@mail.gmail.com' \
--to=anders.roxell@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=shuah@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).