From: Max Reitz <mreitz@redhat.com>
To: tu bo <tubo@linux.vnet.ibm.com>, Kevin Wolf <kwolf@redhat.com>
Cc: armbru@redhat.com, mimu@linux.vnet.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v10 7/7] qemu-iotests: s390x: fix test 130
Date: Sat, 4 Jul 2015 18:17:07 +0200 [thread overview]
Message-ID: <55980703.1070609@redhat.com> (raw)
In-Reply-To: <5594FDD6.2020902@linux.vnet.ibm.com>
On 02.07.2015 11:01, tu bo wrote:
> I got one issue after running checkpatch.pl below,
>
> [gavin@oc6333346435 qemu]$ ./scripts/checkpatch.pl
> home/gavin/patch/v8/0007-qemu-iotests-s390x-fix-test-130.patch //
> ERROR: Invalid UTF-8, patch and commit message should be encoded in
> UTF-8//
> #52: FILE: tests/qemu-iotests/130.out:12://
> +(qemu) commit testdisk//
> ^//
>
> ERROR: Invalid UTF-8, patch and commit message should be encoded in
> UTF-8//
> #60: FILE: tests/qemu-iotests/130.out:19://
> +(qemu) commit testdisk//
> ^//
>
> total: 2 errors, 0 warnings, 36 lines checked/
>
> The reason is that 130.out contains some non-text data. Do I need to
> report an issue to checkpatch.pl, or ignore this error message? thanks
I think ignoring it is fine.
Max
prev parent reply other threads:[~2015-07-04 16:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 3:32 [Qemu-devel] [PATCH v10 0/7] Update tests/qemu-iotests failing cases for the s390 platform Bo Tu
2015-05-29 3:32 ` [Qemu-devel] [PATCH v10 1/7] qemu-iotests: qemu machine type support Bo Tu
2015-05-29 3:32 ` [Qemu-devel] [PATCH v10 2/7] qemu-iotests: run qemu with -nodefaults and fix 067, 071, 081 and 087 Bo Tu
2015-05-29 3:32 ` [Qemu-devel] [PATCH v10 3/7] qemu-iotests: s390x: fix test 041 Bo Tu
2015-05-29 3:32 ` [Qemu-devel] [PATCH v10 4/7] qemu-iotests: s390x: fix test 055 Bo Tu
2015-05-29 3:32 ` [Qemu-devel] [PATCH v10 5/7] qemu-iotests: s390x: fix test 049 Bo Tu
2015-05-29 3:32 ` [Qemu-devel] [PATCH v10 6/7] qemu-iotests: s390x: fix test 051 Bo Tu
2015-05-29 3:32 ` [Qemu-devel] [PATCH v10 7/7] qemu-iotests: s390x: fix test 130 Bo Tu
2015-07-02 9:01 ` tu bo
2015-07-04 16:17 ` Max Reitz [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=55980703.1070609@redhat.com \
--to=mreitz@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mimu@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=tubo@linux.vnet.ibm.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).