Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp1212824pxf; Fri, 12 Mar 2021 04:51:46 -0800 (PST) X-Google-Smtp-Source: ABdhPJxSK9EY7myNlxK6Mq9NOn5+trQxq2R6jayOWvvfMHkxJ1aRXw3gMD3dvdMLAd+Bj1TE3gEL X-Received: by 2002:a17:906:2692:: with SMTP id t18mr8169770ejc.16.1615553506135; Fri, 12 Mar 2021 04:51:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1615553506; cv=none; d=google.com; s=arc-20160816; b=tDzW8x+zztYBJ0q8CmCavdzwXWP+rov69R17Mm/apXTSGQKAYqVTRE/CZvv4S+b4uX dMpwkKeNTNo8cru+NJc/VmCR1f2PdcDaAHrIvTG5CeW2Uq5VqRTaJTwawFMAILdY3Ebb eAesTSA3K4yz2UgnpR+7SN/5pL1P/2v2uXwNUynwDt3t3xqPF1vViSIt19X+pX92JPWQ ugEbuOtMA00HuMXJ72bPi9LtWTjkHEZs9f1bNw6x2hWNE0DQvJq5T3sVWbnB12fSFrfs t1gxp7pvHMDe1GEuVHZezlHlJVdJbJK8ydT9h+0DVSpUFgE5qgpGRcux5Hu37bNktg0/ GUSA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=72e13tYW7nKZfjdFGZqzF4uAPnpQ+x8jciR0p0qAWvk=; b=Gq4BTsRlY4gL8tkL6LD/DflOEjcsX5wNsewuGnlOoFUbsd4hauhZ9QeOJlKbrTB2EQ MkwQZfFnXt/vkKHcGHUn93eTEJIqSHooFCtm5KTwWPI+cCPP2JBKxBQgtdrDQlF+XGZu J63OG/0i9rQczjiKAo8yNt2ulSrVdp513QfuLQ0jEapoNg+neQECwY1K10ZxFsD5H5M5 HIU6P2c4gGygYgotuYNGAe74kb1ud9JaWMvo9Xl9Z4lfCNAkInw9a2CE1ILatOU/fh3H LrWLVtcswT8bLJ2rJl0i24qtdiE/wQK0Lyxk4evLW9FCj21XjROAvJPR9j3ya2kn6ogB xKZQ== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=canonical.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id ss27si3983643ejb.322.2021.03.12.04.51.22; Fri, 12 Mar 2021 04:51:46 -0800 (PST) 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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=canonical.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231741AbhCLMtX (ORCPT + 99 others); Fri, 12 Mar 2021 07:49:23 -0500 Received: from youngberry.canonical.com ([91.189.89.112]:39327 "EHLO youngberry.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231289AbhCLMtD (ORCPT ); Fri, 12 Mar 2021 07:49:03 -0500 Received: from 1.general.cking.uk.vpn ([10.172.193.212]) by youngberry.canonical.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.86_2) (envelope-from ) id 1lKhDx-0004cD-6x; Fri, 12 Mar 2021 12:49:01 +0000 Subject: Re: pinctrl: core: Handling pinmux and pinconf separately To: Andy Shevchenko Cc: Michal Simek , Linus Walleij , "linux-gpio@vger.kernel.org" , "linux-kernel@vger.kernel.org" References: <5c08bd61-688f-e95b-5fa3-584f190ed4bf@xilinx.com> From: Colin Ian King Message-ID: Date: Fri, 12 Mar 2021 12:49:00 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/03/2021 12:45, Andy Shevchenko wrote: > On Thu, Mar 11, 2021 at 1:26 PM Colin Ian King wrote: >> On 11/03/2021 11:16, Michal Simek wrote: >>> On 3/11/21 11:57 AM, Colin Ian King wrote: > >>>> For the PIN_MAP_TYPE_CONFIGS_PIN and PIN_MAP_TYPE_CONFIGS_GROUP >>>> setting->type cases the loop can break out with ret not being set. Since >>>> ret has not been initialized it the ret < 0 check is checking against an >>>> uninitialized value. >>>> >>>> I was not sure if the PIN_MAP_TYPE_CONFIGS_PIN and >>>> PIN_MAP_TYPE_CONFIGS_GROUP cases should be setting ret and if so, what >>>> the value of ret should be set to (is it an error condition or not?). Or >>>> should ret be initialized to 0 or a default error value at the start of >>>> the function. >>>> >>>> Hence I'm reporting this issue. >>> >>> What about this? Is this passing static analysis? >> >> It will take me 2 hours to re-run the analysis, but from eyeballing the >> code I think the assignments will fix this. > > It surprises me that tools in the 21st century can't run on a subset > of the data. > > Had you filed a bug to the Coverity team that they will provide a way > to rerun analysis on a subset of the data? It can. However I need to keep copies of the entire build to do this and I build many different kernels (hence lots of storage required) and rarely do minor change + rebuilds, so I don't cater for this in my test build environment. > >