Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Tvrtko Ursulin <tursulin@ursulin.net>,
	igt-dev@lists.freedesktop.org
Cc: Intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [igt-dev] [PATCH i-g-t] intel-gpu-overlay: Update for renamed tracepoints
Date: Tue, 6 Mar 2018 11:17:13 +0000	[thread overview]
Message-ID: <5ba44ef9-39b2-ab37-b670-74183debeaa5@linux.intel.com> (raw)
In-Reply-To: <152033390046.17960.16792944877596440902@mail.alporthouse.com>


On 06/03/2018 10:58, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2018-03-05 12:41:58)
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> Request tracepoints have been renames so update the tool to be able to
>> find them.
>>
>> Also support falling back to the old name for compatibility.
>>
>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>> ---
>> Compile tested only so also looking for someone to smoke test it if
>> possible. Otherwise I'll do it in due time once back to a test machine
>> with display.
> 
> I use it on remote boxes with ssh -X.

Ha.. never crossed my mind.

>> I was also 50-50 whether it is worth supporting the old names, but it was
>> easy enough so I did it.
> 
> Yeah, but a slippery slope? If we just rule this is a dev tool and using
> it on anything other than drm-tip requires you to fix it up, do we
> create more or less hassle for ourselves?

You're probably right. Will drop the backwards compatibility.

Regards,

Tvrtko

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-03-06 11:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-05 12:41 [igt-dev] [PATCH i-g-t] intel-gpu-overlay: Update for renamed tracepoints Tvrtko Ursulin
2018-03-05 16:14 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2018-03-05 20:39 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-03-06 10:58 ` [igt-dev] [PATCH i-g-t] " Chris Wilson
2018-03-06 11:17   ` Tvrtko Ursulin [this message]
2018-03-15 10:01 ` [igt-dev] [PATCH i-g-t v2] " Tvrtko Ursulin
2018-03-15 10:32   ` [Intel-gfx] " Chris Wilson
2018-03-15 12:24 ` [igt-dev] ✗ Fi.CI.BAT: warning for intel-gpu-overlay: Update for renamed tracepoints (rev2) 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=5ba44ef9-39b2-ab37-b670-74183debeaa5@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=tursulin@ursulin.net \
    /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