Received: by 2002:a25:ef43:0:0:0:0:0 with SMTP id w3csp959772ybm; Wed, 27 May 2020 12:13:23 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyf1zUw/8+SEqvdWqCFu0LoIeHsTWb5Ac4iq3HEXIlcg+sEs+qbmSzmbZR1VENZVOzcF/Aj X-Received: by 2002:a17:906:507:: with SMTP id j7mr7646570eja.426.1590606803365; Wed, 27 May 2020 12:13:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590606803; cv=none; d=google.com; s=arc-20160816; b=eqDkelddC/qFmSF+KAqL/4Lhq0AaVUqV51S2tRts2xf3+pRfKhyf5CF52E1bxY76mH F25I0DobDzVZW3S8TEX/f9aNvn3HPU5RDql5977+7YrISTDwdgns6a/DxuokZWhAgC3G ctSXgjrKJBNsQtHfscF7bo+tmsrAXSCdMjgGacIFj6pauf+oEkiwcf5g8P2Z3qND8QEg pmAX5iwIUU3NU0WmeYXdrd5vyeltqG5z2JsIxw86oLoMa9zj1j4FnxxLqM0yqtKB5/0B goSBJyCwAyijpIYfjlaGDvmpFsWCQ4oTugj0bncWWMCZ2eLsgoduIjQly/HaDZs+cGZ6 k1HA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=uHhJpfFsD/vONvAsVvtz6rjp43VNNhX+VTZ9/q4aMwo=; b=MEZBOUs/nhy2rdf2romQsy/mxN9dUy+onC1nm4Mb9SRT5vmQD2bEBhyT8uZwlEjq3h bV1W0SwPf2qIifGWTeWbBQMvlU+urmDxpLcsXn1XcrhLwNHc1/MieyDe70mjR4t4IYpN 6/9/rhkrzVkQRUeV381Lcigsjz+9XbZAo1fUrRJThvo+ucvoXTMI4Rq1Fmnd/lL2XWQV lh3sbj9NxQxwRis1zWG5PUoC5UUwkswm9H+3/rf1Fx7bDXuAFK3ABAof4rYYjSO+nec6 PuUmvKMOTxPaPFCyNrSswS8TZXdhNYqWT93wiRGfNhrw30h/Ze2iPZupBo1/hbE4zT2E TK9w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=qcAowrrt; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id re28si2446988ejb.647.2020.05.27.12.13.01; Wed, 27 May 2020 12:13:23 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=qcAowrrt; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728703AbgE0Qkj (ORCPT + 98 others); Wed, 27 May 2020 12:40:39 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36700 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725613AbgE0Qkj (ORCPT ); Wed, 27 May 2020 12:40:39 -0400 Received: from mail-pj1-x1042.google.com (mail-pj1-x1042.google.com [IPv6:2607:f8b0:4864:20::1042]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EC4EFC05BD1E for ; Wed, 27 May 2020 09:40:38 -0700 (PDT) Received: by mail-pj1-x1042.google.com with SMTP id q24so1721243pjd.1 for ; Wed, 27 May 2020 09:40:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=uHhJpfFsD/vONvAsVvtz6rjp43VNNhX+VTZ9/q4aMwo=; b=qcAowrrtbV50Kn3dGfOetWYVLFdCRijJDVCzz2/S44hA4cbH0p9CfEm3wLDwR6D/Wp btmYZ+MR9xXEjil125KcKvcbYdDApFmoGX/fbWkynMEgE0pY9g4bDWCqbLtzDuNIiGvv fFmBKEX2N7z7AVUCqDjt8yIeleJGRXo0fpb+D5z1hr1fbXs/lNPteiXUn2/tSSS+obv1 y7PvAkgfEbd3DC8mu3TSgBa5z1lMr3fcQ3orU6lrHvzd5eaH3riVLqF70K7u1TVj+B3u bIRCl9Kbeol6APv2lMwV1VFaz9I1mn9BfPyIvQt9KvlEejktLp8p4yrFa1Dj2DDaluRx clVQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=uHhJpfFsD/vONvAsVvtz6rjp43VNNhX+VTZ9/q4aMwo=; b=cJqfZwGtRjG5nMcDxRIqpW3bWpuhaYr18veBMHjgc+uIY5mS1C0qfOFqzUVbsAQBzt bi8y/yjsfJhfeQvIODCI+WuQZA6y1G02O/eVfyWPL18W6WZkrTx/4H1K0GWiqjZptCbw AWIUkto7KPyFfdLFHmhBPxQdkuwVlHx4ZgLszb7tLYMUVE/dZDz4oriB6yXHNVY8a8BD ZK8VqjLMgnR9vvGD1PX30eAkI1mubbLtUeAN+AR/m/ppLU5AoJoMKBNjNkJZ2qFPgUAg ihT3dPPu6RKySyuTBdPMOJ8k0k5czXvdGx9S3uyOudIPnFGLUbascSSxRW7MxRJR9AVT ZZJA== X-Gm-Message-State: AOAM530cGMYFddKH0HHjYRTH1+ZBIUtIMeahog2MSlZLxT1BgZUqlCgt 6aJzQ+22c4Dpb1DDD9Xt9jE= X-Received: by 2002:a17:90a:1aa3:: with SMTP id p32mr6262456pjp.4.1590597638410; Wed, 27 May 2020 09:40:38 -0700 (PDT) Received: from ubuntu-s3-xlarge-x86 ([2604:1380:4111:8b00::1]) by smtp.gmail.com with ESMTPSA id q145sm2425759pfq.128.2020.05.27.09.40.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 27 May 2020 09:40:37 -0700 (PDT) Date: Wed, 27 May 2020 09:40:35 -0700 From: Nathan Chancellor To: Arnd Bergmann Cc: Kishon Vijay Abraham I , Vinod Koul , Dilip Kota , linux-kernel@vger.kernel.org, clang-built-linux@googlegroups.com Subject: Re: [PATCH] phy: intel: fix enum type mismatch warning Message-ID: <20200527164035.GA1073507@ubuntu-s3-xlarge-x86> References: <20200527134518.908624-1-arnd@arndb.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200527134518.908624-1-arnd@arndb.de> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 27, 2020 at 03:45:06PM +0200, Arnd Bergmann wrote: > clang points out that a local variable is initialized with > an enum value of the wrong type: > > drivers/phy/intel/phy-intel-combo.c:202:34: error: implicit conversion from enumeration type 'enum intel_phy_mode' to different enumeration type 'enum intel_combo_mode' [-Werror,-Wenum-conversion] > enum intel_combo_mode cb_mode = PHY_PCIE_MODE; > ~~~~~~~ ^~~~~~~~~~~~~ > > From reading the code, it seems that this was not only the > wrong type, but not even supposed to be a code path that can > happen in practice. > > Change the code to have no default phy mode but instead return an > error for invalid input. > > Fixes: ac0a95a3ea78 ("phy: intel: Add driver support for ComboPhy") > Signed-off-by: Arnd Bergmann > --- > drivers/phy/intel/phy-intel-combo.c | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > diff --git a/drivers/phy/intel/phy-intel-combo.c b/drivers/phy/intel/phy-intel-combo.c > index c2a35be4cdfb..04f7b0d08742 100644 > --- a/drivers/phy/intel/phy-intel-combo.c > +++ b/drivers/phy/intel/phy-intel-combo.c > @@ -199,7 +199,7 @@ static int intel_cbphy_pcie_dis_pad_refclk(struct intel_cbphy_iphy *iphy) > > static int intel_cbphy_set_mode(struct intel_combo_phy *cbphy) > { > - enum intel_combo_mode cb_mode = PHY_PCIE_MODE; > + enum intel_combo_mode cb_mode; > enum aggregated_mode aggr = cbphy->aggr_mode; > struct device *dev = cbphy->dev; > enum intel_phy_mode mode; > @@ -224,6 +224,8 @@ static int intel_cbphy_set_mode(struct intel_combo_phy *cbphy) > > cb_mode = SATA0_SATA1_MODE; > break; > + default: > + return -EINVAL; > } > > ret = regmap_write(cbphy->hsiocfg, REG_COMBO_MODE(cbphy->bid), cb_mode); > -- > 2.26.2 > I sent an almost identical patch: https://lore.kernel.org/lkml/20200523035043.3305846-1-natechancellor@gmail.com/ I left out the default case since clang warns when a switch on an enum does not handle all the values (compile time scream) versus a run time scream like yours. I don't have a preference for either so: Reviewed-by: Nathan Chancellor