From: Andi Kleen <ak@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2] drm: Print bad EDID notices less often
Date: Thu, 26 Sep 2024 10:40:18 -0700 [thread overview]
Message-ID: <ZvWcghjXLntdsNAn@tassilo> (raw)
In-Reply-To: <871q161gu5.fsf@intel.com>
> > -static void edid_block_status_print(enum edid_block_status status,
> > +static void edid_block_status_print(struct drm_connector *connector,
> > + enum edid_block_status status,
> > const struct edid *block,
> > int block_num)
> > {
> > + if (status != EDID_BLOCK_OK &&
> > + connector &&
> > + !connector->bad_edid_counter++ &&
>
> The status print has no business changing anything. Besides, this
> function gets called per EDID block, not per EDID.
In this case it doesn't matter because the counter only
prints once per life time of a connector structure,
or if it wraps.
I suppose this can be moved into a wrapper.
>
> > + !drm_debug_enabled(DRM_UT_KMS))
>
> If we did that, we might just as well change the pr_* prints to
> drm_dbg_kms() and be done with it.
But that would prevent it always unless debug is set?
I was trying to print it according to counter first. This matches
the existing usage.
-Andi
prev parent reply other threads:[~2024-09-26 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 16:42 [PATCH v2] drm: Print bad EDID notices less often Andi Kleen
2024-09-26 17:10 ` Jani Nikula
2024-09-26 17:40 ` Andi Kleen [this message]
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=ZvWcghjXLntdsNAn@tassilo \
--to=ak@linux.intel.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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.