From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: x86: enable -Werror
Date: Thu, 20 Feb 2020 11:39:17 -0800 [thread overview]
Message-ID: <20200220193917.GH3972@linux.intel.com> (raw)
In-Reply-To: <875zg174rj.fsf@vitty.brq.redhat.com>
On Thu, Feb 20, 2020 at 02:44:00PM +0100, Vitaly Kuznetsov wrote:
> Paolo Bonzini <pbonzini@redhat.com> writes:
>
> > Avoid more embarrassing mistakes.
>
> "avoid more" != "make less" :-)
Ha! "Fail the build so embarrassing mistakes are *really* emabarrassing".
Where there's a will, there's a way. :-)
next prev parent reply other threads:[~2020-02-20 19:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 19:20 [PATCH] KVM: x86: enable -Werror Paolo Bonzini
2020-02-20 13:44 ` Vitaly Kuznetsov
2020-02-20 19:39 ` Sean Christopherson [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-13 1:40 linmiaohe
2020-02-13 3:31 ` Joe Perches
2020-02-13 9:54 ` 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=20200220193917.GH3972@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=vkuznets@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 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).