From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Artyom Tarasenko <atar4qemu@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 1/2 for-2.6] target-sparc: fix Nucleus quad LDD 128 bit access for windowed registers
Date: Thu, 14 Apr 2016 16:59:34 +0100 [thread overview]
Message-ID: <570FBE66.40008@ilande.co.uk> (raw)
In-Reply-To: <CACXAS8DmAXpNvp-52Zm4RNWPAPgwX-iTNHM2k-+RVsb3HFHE1Q@mail.gmail.com>
On 14/04/16 15:49, Artyom Tarasenko wrote:
>> Possibly the DOS line endings are being added by a mail program?
>
> I use git send-email (which uses msmtp). Used to work fine.
>
> Clicking on "download mbox" on
> https://patchwork.ozlabs.org/patch/610402/ and running checkpatch.pl
> reveals no errors.
>
> Are you sure the problem is not on your side?
In that case please accept my apologies - it seems something in that
patch is triggering my mail client to output CR+LF when exporting
messages. If I switch over to mutt then then indeed the patches appear
as they should.
I'm not sure if Richard is around at the moment, but they look trivial
enough and fix some nasty register corruption bugs so I think they are
worth adding to 2.6. If you can re-send with my R-B then I'll send a
pull request.
ATB,
Mark.
prev parent reply other threads:[~2016-04-14 16:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 9:29 [Qemu-devel] [PATCH 1/2 for-2.6] target-sparc: fix Nucleus quad LDD 128 bit access for windowed registers Artyom Tarasenko
2016-04-14 9:29 ` [Qemu-devel] [PATCH 2/2 for-2.6] target-sparc: fix Trap Based Address Register behavior for sparc64 Artyom Tarasenko
2016-04-14 13:43 ` Mark Cave-Ayland
2016-04-14 14:01 ` Artyom Tarasenko
2016-04-14 13:42 ` [Qemu-devel] [PATCH 1/2 for-2.6] target-sparc: fix Nucleus quad LDD 128 bit access for windowed registers Mark Cave-Ayland
2016-04-14 14:04 ` Artyom Tarasenko
2016-04-14 14:20 ` Mark Cave-Ayland
2016-04-14 14:49 ` Artyom Tarasenko
2016-04-14 15:59 ` Mark Cave-Ayland [this message]
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=570FBE66.40008@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=atar4qemu@gmail.com \
--cc=qemu-devel@nongnu.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).