From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752410AbeEPOUw (ORCPT ); Wed, 16 May 2018 10:20:52 -0400 Received: from mga11.intel.com ([192.55.52.93]:2969 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751395AbeEPOUv (ORCPT ); Wed, 16 May 2018 10:20:51 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,390,1520924400"; d="scan'208";a="55745477" From: Jani Nikula To: Colin King , Joonas Lahtinen , Rodrigo Vivi , David Airlie , intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH][V2] drm/i915/dp: fix spelling mistakes: "seqeuncer" and "seqeuencer" In-Reply-To: <87bmdp3y7o.fsf@intel.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <20180509101606.17483-1-colin.king@canonical.com> <87bmdp3y7o.fsf@intel.com> Date: Wed, 16 May 2018 17:23:24 +0300 Message-ID: <871seb1xyb.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 09 May 2018, Jani Nikula wrote: > On Wed, 09 May 2018, Colin King wrote: >> From: Colin Ian King >> >> Trivial fix to spelling mistakes in WARN warning message text and >> in comments: >> >> "seqeuncer", "seqeuencer" -> "sequencer" >> >> Signed-off-by: Colin Ian King > > Reviewed-by: Jani Nikula > > (Waiting for the CI runs before merging.) And pushed to dinq, thanks for the patch. BR, Jani. > >> --- >> >> V2: Also fix seqeuencer in comments >> >> --- >> drivers/gpu/drm/i915/intel_dp.c | 12 ++++++------ >> 1 file changed, 6 insertions(+), 6 deletions(-) >> >> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c >> index dde92e4af5d3..2cc58596ff5a 100644 >> --- a/drivers/gpu/drm/i915/intel_dp.c >> +++ b/drivers/gpu/drm/i915/intel_dp.c >> @@ -513,7 +513,7 @@ vlv_power_sequencer_kick(struct intel_dp *intel_dp) >> uint32_t DP; >> >> if (WARN(I915_READ(intel_dp->output_reg) & DP_PORT_EN, >> - "skipping pipe %c power seqeuncer kick due to port %c being active\n", >> + "skipping pipe %c power sequencer kick due to port %c being active\n", >> pipe_name(pipe), port_name(intel_dig_port->base.port))) >> return; >> >> @@ -554,7 +554,7 @@ vlv_power_sequencer_kick(struct intel_dp *intel_dp) >> /* >> * Similar magic as in intel_dp_enable_port(). >> * We _must_ do this port enable + disable trick >> - * to make this power seqeuencer lock onto the port. >> + * to make this power sequencer lock onto the port. >> * Otherwise even VDD force bit won't work. >> */ >> I915_WRITE(intel_dp->output_reg, DP); >> @@ -3066,11 +3066,11 @@ static void vlv_detach_power_sequencer(struct intel_dp *intel_dp) >> edp_panel_vdd_off_sync(intel_dp); >> >> /* >> - * VLV seems to get confused when multiple power seqeuencers >> + * VLV seems to get confused when multiple power sequencers >> * have the same port selected (even if only one has power/vdd >> * enabled). The failure manifests as vlv_wait_port_ready() failing >> * CHV on the other hand doesn't seem to mind having the same port >> - * selected in multiple power seqeuencers, but let's clear the >> + * selected in multiple power sequencers, but let's clear the >> * port select always when logically disconnecting a power sequencer >> * from a port. >> */ >> @@ -5698,7 +5698,7 @@ intel_dp_init_panel_power_sequencer_registers(struct intel_dp *intel_dp, >> >> /* >> * On some VLV machines the BIOS can leave the VDD >> - * enabled even on power seqeuencers which aren't >> + * enabled even on power sequencers which aren't >> * hooked up to any port. This would mess up the >> * power domain tracking the first time we pick >> * one of these power sequencers for use since >> @@ -5706,7 +5706,7 @@ intel_dp_init_panel_power_sequencer_registers(struct intel_dp *intel_dp, >> * already on and therefore wouldn't grab the power >> * domain reference. Disable VDD first to avoid this. >> * This also avoids spuriously turning the VDD on as >> - * soon as the new power seqeuencer gets initialized. >> + * soon as the new power sequencer gets initialized. >> */ >> if (force_disable_vdd) { >> u32 pp = ironlake_get_pp_control(intel_dp); -- Jani Nikula, Intel Open Source Technology Center