public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: kvm <kvm@vger.kernel.org>, Paolo Bonzini <pbonzini@redhat.com>,
	 Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	 Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org,  "H. Peter Anvin" <hpa@zytor.com>,
	Paul Durrant <paul@xen.org>
Subject: Re: [PATCH v4] KVM: x86/xen: Inject vCPU upcall vector when local APIC is enabled
Date: Tue, 6 Feb 2024 11:49:54 -0800	[thread overview]
Message-ID: <ZcKNYq5OZxkSs_Z2@google.com> (raw)
In-Reply-To: <17435518cb127e7c1493edac09704623de9ae3f8.camel@infradead.org>

On Tue, Feb 06, 2024, David Woodhouse wrote:
> On Tue, 2024-02-06 at 11:19 -0800, Sean Christopherson wrote:
> > 
> > Patch is corrupt.
> > 
> > git am /home/seanjc/patches/v4_20240116_dwmw2_kvm_x86_xen_inject_vcpu_upcall_vector_when_local_apic_is_enabled.mbx
> > Applying: KVM: x86/xen: Inject vCPU upcall vector when local APIC is enabled
> > error: corrupt patch at line 17
> > 
> > cat ~/patches/v4_20240116_dwmw2_kvm_x86_xen_inject_vcpu_upcall_vector_when_local_apic_is_enabled.mbx | patch -p 1 --merge
> > patching file arch/x86/kvm/lapic.c
> > patch: **** malformed patch at line 59:  #include "ioapic.h"
> > 
> > Based on what I see in a web view, I suspect something on your end is converting
> > whitespace to fancy unicode equivalents.
> > 
> > diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c
> > index 3242f3da2457..75bc7d3f0022 100644
> > --- a/arch/x86/kvm/lapic.c
> > +++ b/arch/x86/kvm/lapic.c
> > @@ -41,6 +41,7 @@
> > =C2=A0#include "ioapic.h"
> > =C2=A0#include "trace.h"
> > =C2=A0#include "x86.h"
> 
> That isn't Unicode. Well, it *is*, but it's the subset of Unicode which
> is also plain old legacy 8-bit ISO8859-1. For some reason, Evolution
> has converted those spaces to non-breaking spaces. I have no idea why
> it's suddenly started doing that; this is a Long Term Nosupport distro
> that $employer forces me to use, and it hasn't even been updated for
> over a year.

Out of genuine curiosity, why not use `git send-email`?

> The patch is in
> https://git.infradead.org/?p=users/dwmw2/linux.git;a=shortlog;h=refs/heads/xenfv
> where I'd gathered everything that was pending, but if you prefer I'll
> also resend it later when I deal with the locking thing we discussed a
> few minutes ago. 

I'd prefer a resend so that I generate a lore link to exactly what I applied.
No rush on either patch, I'm going to be mostly offline from now-ish through
tomorrow.

  reply	other threads:[~2024-02-06 19:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-16 19:00 [PATCH v4] KVM: x86/xen: Inject vCPU upcall vector when local APIC is enabled David Woodhouse
2024-02-06 19:19 ` Sean Christopherson
2024-02-06 19:26   ` David Woodhouse
2024-02-06 19:49     ` Sean Christopherson [this message]
2024-02-06 19:55       ` David Woodhouse
2024-02-14 16:32 ` Michal Luczaj
2024-02-17 11:25   ` David Woodhouse

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=ZcKNYq5OZxkSs_Z2@google.com \
    --to=seanjc@google.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=dwmw2@infradead.org \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paul@xen.org \
    --cc=pbonzini@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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