Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp99409ybi; Thu, 1 Aug 2019 15:23:18 -0700 (PDT) X-Google-Smtp-Source: APXvYqyLirPJjvi+hzrzPALet0zVgx0VMIl7Qiu3RKs2MW7jzLRlysRTC9nc2FNCza340GwbjVzX X-Received: by 2002:a63:fe17:: with SMTP id p23mr23075646pgh.103.1564698198369; Thu, 01 Aug 2019 15:23:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1564698198; cv=none; d=google.com; s=arc-20160816; b=X1K8IpkzZvKm4ES3Zjf9eTD4WJvU97mIsRrxRMv+3EXQecbAGEsj1EXJ9Lb8YXooe3 uebhwbyfhVnrvUMb/d4T5DYOhDcpxf42bU99qYPN8R8bq24QK7V7aUO+GbvtDXhn43iE 4tO8jcO9l0pT6etXKBZVYfiE3tqhAn6UbXCsITY9K97VTFGhnTQvBx0m5lo1yCQL5u2K sjB1ghmmOiExlc2rNRKVj0BqT0QB+hrNS7TCKcJJ5iFmF3DU0AJlfMKuLpCTB8HV553a 4dn1sfqaVF36h5n2ZjTCR4IUs6WKfPRbwUAWKPaP+Ww2BkEw1KF5RN6rLxaaoWTeRaDX PJlA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=MeHlYtoS1R6CHY0m2jJTD6kiPunIHK35K1dbohB/ppI=; b=WZYqG9/YiTmKB2MQGQuxCC46/LQYX6uND9Ry8EVrK9wuBBFHYhw6XAw/d9N7H6/jff vm2rA26ID0Qu0pe39ILYvOmTutWU7U4Ch0AegnNZ1sYFA0pD9UDkkRDdRrojwOFRCCyf 3VCF+/1h/2ILPE74aFpvqUxOtUCkhgC+ktL6nXAMyzknlg3rBQDF58T5E7+gzakVT5Uu PmE6T5rZQpDXLFuDGFVjWQe0Ao2+cU/HnYZFcBvAADhDLPicY6FLlJdES+krpGa10CQu Oq8/8QFFf6elrhNWV36L6Gfra0zZCFmISz5f/hRJi0IeVeRhGvYbD7ujZlUbuzz/RgZl lkYQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="WT2m9/Zm"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k11si35955056pfi.3.2019.08.01.15.23.02; Thu, 01 Aug 2019 15:23:18 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="WT2m9/Zm"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1733019AbfHAQek (ORCPT + 99 others); Thu, 1 Aug 2019 12:34:40 -0400 Received: from mail.kernel.org ([198.145.29.99]:35944 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727024AbfHAQek (ORCPT ); Thu, 1 Aug 2019 12:34:40 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id E93342087E; Thu, 1 Aug 2019 16:34:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1564677279; bh=9dtaBDceSfT8Z//OdbDVGNrZL3XEU07S5L41ZyczgiA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=WT2m9/ZmMm0l9PwXVJS7ub8v7biP+JM2Y62c28yiUZZ9QKXP7twRdPLWgFwI4CO4F k/1R4ZL6/6F4iTr36TLbdNoALaNlJcTjdVXH9jp/L9E86sebkQn7zHNsLDvNsWaymg BpnOw0a1dhTCoN5oX6ebUvNpETCnfOT8vSmT4l+4= Date: Thu, 1 Aug 2019 18:34:37 +0200 From: Greg KH To: Harsh Jain Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] staging:kpc2000:Fix dubious x | !y sparse warning Message-ID: <20190801163437.GA8360@kroah.com> References: <20190731183606.2513-1-harshjain32@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190731183606.2513-1-harshjain32@gmail.com> User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 01, 2019 at 12:06:06AM +0530, Harsh Jain wrote: > Bitwise OR(|) operation with 0 always yield same result. > It fixes dubious x | !y sparse warning. > > Signed-off-by: Harsh Jain > --- > drivers/staging/kpc2000/kpc2000_i2c.c | 16 +--------------- > 1 file changed, 1 insertion(+), 15 deletions(-) > > diff --git a/drivers/staging/kpc2000/kpc2000_i2c.c b/drivers/staging/kpc2000/kpc2000_i2c.c > index b108da4..5f027d7c 100644 > --- a/drivers/staging/kpc2000/kpc2000_i2c.c > +++ b/drivers/staging/kpc2000/kpc2000_i2c.c > @@ -536,29 +536,15 @@ static u32 i801_func(struct i2c_adapter *adapter) > > u32 f = > I2C_FUNC_I2C | /* 0x00000001 (I enabled this one) */ > - !I2C_FUNC_10BIT_ADDR | /* 0x00000002 */ > - !I2C_FUNC_PROTOCOL_MANGLING | /* 0x00000004 */ > ((priv->features & FEATURE_SMBUS_PEC) ? I2C_FUNC_SMBUS_PEC : 0) | /* 0x00000008 */ > - !I2C_FUNC_SMBUS_BLOCK_PROC_CALL | /* 0x00008000 */ > I2C_FUNC_SMBUS_QUICK | /* 0x00010000 */ > - !I2C_FUNC_SMBUS_READ_BYTE | /* 0x00020000 */ > - !I2C_FUNC_SMBUS_WRITE_BYTE | /* 0x00040000 */ > - !I2C_FUNC_SMBUS_READ_BYTE_DATA | /* 0x00080000 */ > - !I2C_FUNC_SMBUS_WRITE_BYTE_DATA | /* 0x00100000 */ > - !I2C_FUNC_SMBUS_READ_WORD_DATA | /* 0x00200000 */ > - !I2C_FUNC_SMBUS_WRITE_WORD_DATA | /* 0x00400000 */ > - !I2C_FUNC_SMBUS_PROC_CALL | /* 0x00800000 */ > - !I2C_FUNC_SMBUS_READ_BLOCK_DATA | /* 0x01000000 */ > - !I2C_FUNC_SMBUS_WRITE_BLOCK_DATA | /* 0x02000000 */ This is ok, it is showing you that these bits are explicitly being not set. Which is good, now you can go through the list and see that all are accounted for. So I think this should stay as-is, thanks. greg k-h