From: Jani Nikula <jani.nikula@linux.intel.com>
To: Clint Taylor <clinton.a.taylor@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/dvo: fix debug logging on unknown DID
Date: Thu, 01 Jun 2017 15:57:34 +0300 [thread overview]
Message-ID: <87lgpbj269.fsf@intel.com> (raw)
In-Reply-To: <53c47246-e5dc-3db1-299e-c9ca8aa4a9a1@intel.com>
On Wed, 31 May 2017, Clint Taylor <clinton.a.taylor@intel.com> wrote:
> On 05/31/2017 03:16 AM, Jani Nikula wrote:
>> Print DID not VID on the DID error path. Looks like a copy-paste error
>> from the VID error path. Clarify and clean up error logging, making them
>> distinguishable from each other, while at it.
>
> Reviewed-by: Clinton Taylor <clinton.a.taylor@intel.com>
Thanks, pushed to drm-intel-next-queued.
BR,
Jani.
>
> -Clint
>
>>
>> Reported-by: Petru Mihancea <petrum@gmail.com>
>> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=101243
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>> drivers/gpu/drm/i915/dvo_ch7xxx.c | 10 ++++------
>> 1 file changed, 4 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/dvo_ch7xxx.c b/drivers/gpu/drm/i915/dvo_ch7xxx.c
>> index 44b3159f2fe8..7aeeffd2428b 100644
>> --- a/drivers/gpu/drm/i915/dvo_ch7xxx.c
>> +++ b/drivers/gpu/drm/i915/dvo_ch7xxx.c
>> @@ -217,9 +217,8 @@ static bool ch7xxx_init(struct intel_dvo_device *dvo,
>>
>> name = ch7xxx_get_id(vendor);
>> if (!name) {
>> - DRM_DEBUG_KMS("ch7xxx not detected; got 0x%02x from %s "
>> - "slave %d.\n",
>> - vendor, adapter->name, dvo->slave_addr);
>> + DRM_DEBUG_KMS("ch7xxx not detected; got VID 0x%02x from %s slave %d.\n",
>> + vendor, adapter->name, dvo->slave_addr);
>> goto out;
>> }
>>
>> @@ -229,9 +228,8 @@ static bool ch7xxx_init(struct intel_dvo_device *dvo,
>>
>> devid = ch7xxx_get_did(device);
>> if (!devid) {
>> - DRM_DEBUG_KMS("ch7xxx not detected; got 0x%02x from %s "
>> - "slave %d.\n",
>> - vendor, adapter->name, dvo->slave_addr);
>> + DRM_DEBUG_KMS("ch7xxx not detected; got DID 0x%02x from %s slave %d.\n",
>> + device, adapter->name, dvo->slave_addr);
>> goto out;
>> }
>>
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-06-01 12:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 10:16 [PATCH] drm/i915/dvo: fix debug logging on unknown DID Jani Nikula
2017-05-31 10:51 ` ✗ Fi.CI.BAT: failure for " Patchwork
2017-05-31 17:55 ` [PATCH] " Clint Taylor
2017-06-01 12:57 ` Jani Nikula [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=87lgpbj269.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=clinton.a.taylor@intel.com \
--cc=intel-gfx@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 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.