public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 6/7] drm/i915: prettify MST debug message
Date: Fri, 11 Oct 2019 20:14:32 +0300	[thread overview]
Message-ID: <20191011171432.GT1208@intel.com> (raw)
In-Reply-To: <20191011170832.cvbcoqji3wyjv3ij@ldmartin-desk1>

On Fri, Oct 11, 2019 at 10:08:32AM -0700, Lucas De Marchi wrote:
> On Fri, Oct 11, 2019 at 03:08:50PM +0300, Ville Syrjälä wrote:
> >On Thu, Oct 10, 2019 at 06:09:06PM -0700, Lucas De Marchi wrote:
> >> s/?/:/ so it's get correctly colored by dmesg.
> >
> >What do you mean correctly?
> >
> >The debug message was asking the question "(is) MST supported?"
> >After this it just declares that MST is not supported. I guess no real
> >difference so I could live with either one.
> >
> >The only thing that slightly bothers me with the ':' is that the
> >port/sink/modparam also use it, but in a slightly different way
> >so the "MST supported:" ':' looks a bit naked.
> 
> What I mean is that dmesg uses the first ":" after [] to colorize.
> 
> Before:
> *[ENCODER:xx:yyy] MST support? port:* yes, sink: yes, modparam: yes
> 
> After:
> *[ENCODER:xx:yyy] MST support:* port: yes, sink: yes, modparam: yes

Ah, I guess I so routinely pipe it to a file/less that haven't really
noticed :)

> 
> Not really important, just makes more sense IMO.

You've convinced me.

> 
> Lucas De Marchi
> 
> >
> >Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> >>
> >> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> >> ---
> >>  drivers/gpu/drm/i915/display/intel_dp.c | 2 +-
> >>  1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> >> index 348a09890611..33a55da89ce9 100644
> >> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> >> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> >> @@ -4450,7 +4450,7 @@ intel_dp_configure_mst(struct intel_dp *intel_dp)
> >>  		&dp_to_dig_port(intel_dp)->base;
> >>  	bool sink_can_mst = intel_dp_sink_can_mst(intel_dp);
> >>
> >> -	DRM_DEBUG_KMS("[ENCODER:%d:%s] MST support? port: %s, sink: %s, modparam: %s\n",
> >> +	DRM_DEBUG_KMS("[ENCODER:%d:%s] MST support: port: %s, sink: %s, modparam: %s\n",
> >>  		      encoder->base.base.id, encoder->base.name,
> >>  		      yesno(intel_dp->can_mst), yesno(sink_can_mst),
> >>  		      yesno(i915_modparams.enable_dp_mst));
> >> --
> >> 2.23.0
> >>
> >> _______________________________________________
> >> Intel-gfx mailing list
> >> Intel-gfx@lists.freedesktop.org
> >> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
> >
> >-- 
> >Ville Syrjälä
> >Intel

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

  reply	other threads:[~2019-10-11 17:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-11  1:09 [PATCH 0/7] Small fixes before fixing MST Lucas De Marchi
2019-10-11  1:09 ` [PATCH 1/7] drm/i915: simplify setting of ddi_io_power_domain Lucas De Marchi
2019-10-11 18:01   ` Souza, Jose
2019-10-11  1:09 ` [PATCH 2/7] drm/i915: cleanup unused returns on DP-MST Lucas De Marchi
2019-10-11 11:48   ` Ville Syrjälä
2019-10-14 18:04     ` Lucas De Marchi
2019-10-11  1:09 ` [PATCH 3/7] drm/i915: fix port checks for MST support on gen >= 11 Lucas De Marchi
2019-10-11 12:02   ` Ville Syrjälä
2019-10-11  1:09 ` [PATCH 4/7] drm/i915: remove extra new line on pipe_config mismatch Lucas De Marchi
2019-10-11 12:05   ` Ville Syrjälä
2019-10-11  1:09 ` [PATCH 5/7] drm/i915: add pipe name to pipe mismatch logs Lucas De Marchi
2019-10-11 12:05   ` Ville Syrjälä
2019-10-11  1:09 ` [PATCH 6/7] drm/i915: prettify MST debug message Lucas De Marchi
2019-10-11 12:08   ` Ville Syrjälä
2019-10-11 17:08     ` Lucas De Marchi
2019-10-11 17:14       ` Ville Syrjälä [this message]
2019-10-11 17:22         ` Lucas De Marchi
2019-10-11  1:09 ` [PATCH 7/7] drm/dp-mst: fix warning on unused var Lucas De Marchi
2019-10-11 17:58   ` Lucas De Marchi
2019-10-14 17:47     ` Daniel Vetter
2019-10-11 18:03   ` Souza, Jose
2019-10-11  1:45 ` ✗ Fi.CI.CHECKPATCH: warning for Small fixes before fixing MST Patchwork
2019-10-11  1:47 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-10-11  2:05 ` ✓ Fi.CI.BAT: success " Patchwork
2019-10-11 14:26 ` ✓ 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=20191011171432.GT1208@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox