From: Jani Nikula <jani.nikula@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Subject: Re: [PATCH] drm/i915: Typo fix - 'pipe bpc' to 'pipe bpp'
Date: Wed, 05 Apr 2017 11:41:00 +0300 [thread overview]
Message-ID: <878tnf1c2r.fsf@intel.com> (raw)
In-Reply-To: <87bmsb1edy.fsf@intel.com>
On Wed, 05 Apr 2017, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Tue, 04 Apr 2017, Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com> wrote:
>> Noticed this while I was looking at some debug output,
>> [drm:intel_hdmi_compute_config [i915]] picking bpc to 12 for HDMI output
>> [drm:intel_hdmi_compute_config [i915]] forcing pipe bpc to 36 for HDMI
>>
>> I believe the second line should be pipe *bpp*
>>
>> Signed-off-by: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
>
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
And pushed, thanks for the patch.
BR,
Jani.
>
>
>> ---
>> drivers/gpu/drm/i915/intel_hdmi.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_hdmi.c b/drivers/gpu/drm/i915/intel_hdmi.c
>> index 1d623b5..6efc3cb 100644
>> --- a/drivers/gpu/drm/i915/intel_hdmi.c
>> +++ b/drivers/gpu/drm/i915/intel_hdmi.c
>> @@ -1392,7 +1392,7 @@ bool intel_hdmi_compute_config(struct intel_encoder *encoder,
>> }
>>
>> if (!pipe_config->bw_constrained) {
>> - DRM_DEBUG_KMS("forcing pipe bpc to %i for HDMI\n", desired_bpp);
>> + DRM_DEBUG_KMS("forcing pipe bpp to %i for HDMI\n", desired_bpp);
>> pipe_config->pipe_bpp = desired_bpp;
>> }
--
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-04-05 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 18:16 [PATCH] drm/i915: Typo fix - 'pipe bpc' to 'pipe bpp' Dhinakaran Pandiyan
2017-04-04 18:36 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-04-05 7:51 ` [PATCH] " Jani Nikula
2017-04-05 8:41 ` 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=878tnf1c2r.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dhinakaran.pandiyan@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.