qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: famz@redhat.com, peter.maydell@linaro.org
Subject: Re: [Qemu-devel] [PULL 0/3] Tracing patches
Date: Tue, 30 Jan 2018 11:58:57 +0000	[thread overview]
Message-ID: <20180130115857.GA15551@stefanha-x1.localdomain> (raw)
In-Reply-To: <151724248550.788.16657123948321508466@5adcb62bf0d6>

[-- Attachment #1: Type: text/plain, Size: 1413 bytes --]

On Mon, Jan 29, 2018 at 08:14:46AM -0800, no-reply@patchew.org wrote:
> === OUTPUT BEGIN ===
> Checking PATCH 1/3: tracetool: prefix parse errors with line numbers...
> Checking PATCH 2/3: tracetool: clarify that "formats" means "format strings"...
> ERROR: line over 90 characters
> #39: FILE: scripts/tracetool/__init__.py:240:
> +            raise ValueError("Only events with 'tcg' property can have two format strings")
> 
> WARNING: line over 80 characters
> #42: FILE: scripts/tracetool/__init__.py:242:
> +            raise ValueError("Events with 'tcg' property must have two format strings")
> 
> total: 1 errors, 1 warnings, 27 lines checked
> 
> Your patch has style problems, please review.  If any of these errors
> are false positives report them to the maintainer, see
> CHECKPATCH in MAINTAINERS.
> 
> Checking PATCH 3/3: tracetool: report error on foo() instead of foo(void)...
> WARNING: line over 80 characters
> #26: FILE: scripts/tracetool/__init__.py:79:
> +                raise ValueError("Empty argument (did you forget to use 'void'?)")
> 
> total: 0 errors, 1 warnings, 8 lines checked
> 
> Your patch has style problems, please review.  If any of these errors
> are false positives report them to the maintainer, see
> CHECKPATCH in MAINTAINERS.
> === OUTPUT END ===

For the record, I didn't wrap these error messages so that grep(1)
works.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

  reply	other threads:[~2018-01-30 15:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-29 16:07 [Qemu-devel] [PULL 0/3] Tracing patches Stefan Hajnoczi
2018-01-29 16:07 ` [Qemu-devel] [PULL 1/3] tracetool: prefix parse errors with line numbers Stefan Hajnoczi
2018-01-29 16:07 ` [Qemu-devel] [PULL 2/3] tracetool: clarify that "formats" means "format strings" Stefan Hajnoczi
2018-01-29 16:07 ` [Qemu-devel] [PULL 3/3] tracetool: report error on foo() instead of foo(void) Stefan Hajnoczi
2018-01-29 16:14 ` [Qemu-devel] [PULL 0/3] Tracing patches no-reply
2018-01-30 11:58   ` Stefan Hajnoczi [this message]
2018-01-30 10:50 ` Peter Maydell
  -- strict thread matches above, loose matches on Subject: below --
2019-09-18 13:21 Stefan Hajnoczi
2019-09-19 13:37 ` Peter Maydell
2018-02-19 16:19 Stefan Hajnoczi
2018-02-19 18:40 ` Peter Maydell
2017-03-16  7:04 Stefan Hajnoczi
2017-03-16 15:31 ` Peter Maydell
2016-09-05 19:42 Stefan Hajnoczi
2016-09-06 12:32 ` Peter Maydell
2012-03-30 10:58 Stefan Hajnoczi
2012-04-02 15:52 ` Anthony Liguori

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=20180130115857.GA15551@stefanha-x1.localdomain \
    --to=stefanha@redhat.com \
    --cc=famz@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).