Seiji Aguchi <[email protected]> writes:

> Anthony,
>
>> Currently my company doesn't allow me to use git-send-email to send a email.
>> So now I'm trying to find work around with IT.
>
> Satoru and I still talk if we can use git-send-email with my company IT.
> But, it seems to  take a long time...
>
> So, I attached Satoru's patch.
> Could you please apply it to your tree?

Even attached, the patch still has carriage returns.  I don't have a lot
of confidence in accept a patch if it cannot be submitted in the correct
fashion at least.

Regards,

Anthony Liguori

>
> Seiji
>
>> -----Original Message-----
>> From: Satoru Moriya
>> Sent: Thursday, March 28, 2013 12:43 AM
>> To: Anthony Liguori; [email protected]
>> Cc: Jan Kiszka; [email protected]; Paolo Bonzini; Seiji Aguchi; Tomoki 
>> Sekiyama; [email protected];
>> [email protected]
>> Subject: RE: [Qemu-devel] [PATCH v4] Add option to mlock qemu and guest 
>> memory
>> 
>> > -----Original Message-----
>> > From: Anthony Liguori [mailto:[email protected]]
>> > Sent: Wednesday, March 27, 2013 11:18 AM
>> > To: Satoru Moriya; [email protected]
>> > Cc: Jan Kiszka; [email protected]; Paolo Bonzini; Seiji Aguchi;
>> > Tomoki Sekiyama; dle- [email protected];
>> > [email protected]
>> > Subject: Re: [Qemu-devel] [PATCH v4] Add option to mlock qemu and
>> > guest memory
>> >
>> > Satoru Moriya <[email protected]> writes:
>> >
>> > > In certain scenario, latency induced by paging is significant and
>> > > memory locking is needed. Also, in the scenario with untrusted
>> > > guests, latency improvement due to mlock is desired.
>> > >
>> > > This patch introduces a following new option to mlock guest and qemu
>> > > memory:
>> > >
>> > > -realtime mlock=on|off
>> > >
>> > > Signed-off-by: Satoru Moriya <[email protected]>
>> > > Reviewed-by: Paolo Bonzini <[email protected]>
>> > > Reviewed-by: Marcelo Tosatti <[email protected]>
>> >
>> > This patch doesn't apply because you're sending it MIME encoded and
>> > the patch has carriage returns in it.  I think your mailer is badly 
>> > munging the patch.
>> >
>> > Please send it via git-send-email directly from the repository.
>> 
>> I'm sorry for bothering you...
>> 
>> Currently my company doesn't allow me to use git-send-email to send a email.
>> So now I'm trying to find work around with IT.
>> 
>> Once it is solved, I re-post the patch.
>> 
>> Regards,
>> Satoru


Reply via email to