From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751497AbdKVUyv (ORCPT ); Wed, 22 Nov 2017 15:54:51 -0500 Received: from mail-ua0-f177.google.com ([209.85.217.177]:33312 "EHLO mail-ua0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751274AbdKVUyu (ORCPT ); Wed, 22 Nov 2017 15:54:50 -0500 X-Google-Smtp-Source: AGs4zMarcN+EKZtHLoHrIh10mr5EE9cM5AuUcxIGPhugqcF+nHeTCd8BXUHEtgssCZr+KT6+p0qn2zDXxxhItSzIDOE= MIME-Version: 1.0 From: Kees Cook Date: Wed, 22 Nov 2017 12:54:49 -0800 Message-ID: Subject: i915: enum intel_dpll_id cast To: Rodrigo Vivi Cc: Mika Kahola , intel-gfx@lists.freedesktop.org, LKML Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, While doing Clang test builds, this was reported: drivers/gpu/drm/i915/intel_ddi.c:1481:30: warning: implicit conversion from enumeration type 'enum port' to different enumeration type 'enum intel_dpll_id' [-Wenum-conversion] enum intel_dpll_id pll_id = port; ~~~~~~ ^~~~ Which is from: static void bxt_ddi_clock_get(struct intel_encoder *encoder, struct intel_crtc_state *pipe_config) { struct drm_i915_private *dev_priv = to_i915(encoder->base.dev); enum port port = intel_ddi_get_encoder_port(encoder); enum intel_dpll_id pll_id = port; pipe_config->port_clock = bxt_calc_pll_link(dev_priv, pll_id); ... } In looking at it, it seems to be harmless if as enum port has a smaller range than enum intel_dpll_id. I just wanted to check if maybe something might go weird, since DPLL_ID_LCPLL_2700 maybe ends up getting seen as I915_MAX_PORTS? enum port { PORT_NONE = -1, PORT_A = 0, PORT_B, PORT_C, PORT_D, PORT_E, I915_MAX_PORTS }; enum intel_dpll_id { ... DPLL_ID_LCPLL_2700 = 5, ... }; Thanks! -Kees -- Kees Cook Pixel Security