From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 2/3] overlay: reindent tracepoint parser
Date: Thu, 1 Feb 2018 17:51:57 +0000 [thread overview]
Message-ID: <f784c7dd-5c39-5d53-622e-bb9ecfb2ea96@intel.com> (raw)
In-Reply-To: <151750725181.28099.10005546661571881061@mail.alporthouse.com>
On 01/02/18 17:47, Chris Wilson wrote:
> Quoting Lionel Landwerlin (2018-02-01 17:32:15)
>> I wrote it, but couldn't reread myself... This doesn't contain any
>> change apart from reindenting.
>>
>> Signed-off-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
> Skimmed the changes looking for non-mechanical changes, so assuming the
> indentation isn't part of the parser (*cough* python *cough*),
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> -Chris
>
It's not.
And I don't get python ;)
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2018-02-01 17:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 17:32 [igt-dev] [PATCH i-g-t 1/3] overlay: add missing foreground option Lionel Landwerlin
2018-02-01 17:32 ` [igt-dev] [PATCH i-g-t 2/3] overlay: reindent tracepoint parser Lionel Landwerlin
2018-02-01 17:47 ` Chris Wilson
2018-02-01 17:51 ` Lionel Landwerlin [this message]
2018-02-01 17:32 ` [igt-dev] [PATCH i-g-t 3/3] overlay: fix invalid pointer access Lionel Landwerlin
2018-02-01 17:46 ` Chris Wilson
2018-02-01 17:44 ` [igt-dev] [PATCH i-g-t 1/3] overlay: add missing foreground option Chris Wilson
2018-02-01 17:52 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/3] " Patchwork
2018-02-01 21:34 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
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=f784c7dd-5c39-5d53-622e-bb9ecfb2ea96@intel.com \
--to=lionel.g.landwerlin@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.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