From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Gustavo A. R. Silva" <garsilva@embeddedor.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
David Airlie <airlied@linux.ie>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
"Gustavo A. R. Silva" <garsilva@embeddedor.com>,
Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [PATCH] drm/i915/intel_sdvo: mark expected switch fall-throughs
Date: Thu, 09 Nov 2017 11:13:54 +0200 [thread overview]
Message-ID: <87lgjfak6l.fsf@intel.com> (raw)
In-Reply-To: <87wp2zammy.fsf@intel.com>
On Thu, 09 Nov 2017, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Wed, 08 Nov 2017, "Gustavo A. R. Silva" <garsilva@embeddedor.com> wrote:
>> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
>> where we are expecting to fall through.
>>
>> Addresses-Coverity-ID: 141432
>> Addresses-Coverity-ID: 141433
>> Addresses-Coverity-ID: 141434
>> Addresses-Coverity-ID: 141435
>> Addresses-Coverity-ID: 141436
>> Signed-off-by: Gustavo A. R. Silva <garsilva@embeddedor.com>
>
> Acked-by: Jani Nikula <jani.nikula@intel.com>
More explicitly, the patch looks good, but I'll give others the chance
to chime in before merging. In particular Chris has been doing plenty of
warning fixes lately.
BR,
Jani.
>
>> ---
>> drivers/gpu/drm/i915/intel_sdvo.c | 11 ++++++-----
>> 1 file changed, 6 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_sdvo.c b/drivers/gpu/drm/i915/intel_sdvo.c
>> index 7437944..921e372 100644
>> --- a/drivers/gpu/drm/i915/intel_sdvo.c
>> +++ b/drivers/gpu/drm/i915/intel_sdvo.c
>> @@ -1327,6 +1327,7 @@ static void intel_sdvo_pre_enable(struct intel_encoder *intel_encoder,
>> switch (crtc_state->pixel_multiplier) {
>> default:
>> WARN(1, "unknown pixel multiplier specified\n");
>> + /* fall through */
>> case 1: rate = SDVO_CLOCK_RATE_MULT_1X; break;
>> case 2: rate = SDVO_CLOCK_RATE_MULT_2X; break;
>> case 4: rate = SDVO_CLOCK_RATE_MULT_4X; break;
>> @@ -2274,15 +2275,15 @@ intel_sdvo_guess_ddc_bus(struct intel_sdvo *sdvo)
>> */
>> switch (sdvo->controlled_output) {
>> case SDVO_OUTPUT_LVDS1:
>> - mask |= SDVO_OUTPUT_LVDS1;
>> + mask |= SDVO_OUTPUT_LVDS1; /* fall through */
>> case SDVO_OUTPUT_LVDS0:
>> - mask |= SDVO_OUTPUT_LVDS0;
>> + mask |= SDVO_OUTPUT_LVDS0; /* fall through */
>> case SDVO_OUTPUT_TMDS1:
>> - mask |= SDVO_OUTPUT_TMDS1;
>> + mask |= SDVO_OUTPUT_TMDS1; /* fall through */
>> case SDVO_OUTPUT_TMDS0:
>> - mask |= SDVO_OUTPUT_TMDS0;
>> + mask |= SDVO_OUTPUT_TMDS0; /* fall through */
>> case SDVO_OUTPUT_RGB1:
>> - mask |= SDVO_OUTPUT_RGB1;
>> + mask |= SDVO_OUTPUT_RGB1; /* fall through */
>> case SDVO_OUTPUT_RGB0:
>> mask |= SDVO_OUTPUT_RGB0;
>> break;
--
Jani Nikula, Intel Open Source Technology Center
prev parent reply other threads:[~2017-11-09 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 20:27 [PATCH] drm/i915/intel_sdvo: mark expected switch fall-throughs Gustavo A. R. Silva
2017-11-09 8:20 ` Jani Nikula
2017-11-09 9:13 ` 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=87lgjfak6l.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@linux.ie \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=garsilva@embeddedor.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@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