From: Chris Wilson <chris@chris-wilson.co.uk>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Prefer encoder->name over port_name()
Date: Fri, 30 Aug 2019 21:27:33 +0100 [thread overview]
Message-ID: <156719685349.29078.13778904979594930276@skylake-alporthouse-com> (raw)
In-Reply-To: <20190830182719.32608-1-ville.syrjala@linux.intel.com>
Quoting Ville Syrjala (2019-08-30 19:27:19)
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> enum port is a mess now because it no longer matches the spec
> at all. Let's start to dig ourselves out of this hole by
> reducing our reliance on port_name(). This should at least make
> a bunch of debug messages a bit more sensible while we think how
> to fill the the hole properly.
>
> Based on the following cocci script with a lot of manual cleanup
> (all the format strings etc.):
> @@
> expression E;
> @@
> (
> - port_name(E->port)
> + E->base.base.id, E->base.name
> |
> - port_name(E.port)
> + E.base.base.id, E.base.name
> )
>
> @@
> enum port P;
> expression E;
> @@
> P = E->port
> <...
> - port_name(P)
> + E->base.base.id, E->base.name
> ...>
>
> @@
> enum port P;
> expression E;
> @@
> P = E.port
> <...
> - port_name(P)
> + E.base.base.id, E.base.name
> ...>
>
> @@
> expression E;
> @@
> {
> - enum port P = E;
> ... when != P
> }
>
The conversions looks correct and ENCODER:%d will help tally the various
debug messages, so
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-08-30 20:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 18:27 [PATCH] drm/i915: Prefer encoder->name over port_name() Ville Syrjala
2019-08-30 20:27 ` Chris Wilson [this message]
2019-08-30 23:07 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-08-31 21:43 ` ✓ Fi.CI.IGT: " 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=156719685349.29078.13778904979594930276@skylake-alporthouse-com \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.