Received: by 10.223.185.116 with SMTP id b49csp1031398wrg; Fri, 16 Feb 2018 11:08:27 -0800 (PST) X-Google-Smtp-Source: AH8x225Bb1KH6j/XY1FsEcOJx8hzhfWxJwlz/4N2UbqOVgXEgUFQ8KJyVHFXy7G24wwfD9oPxm/r X-Received: by 10.98.74.20 with SMTP id x20mr7018771pfa.191.1518808107182; Fri, 16 Feb 2018 11:08:27 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518808107; cv=none; d=google.com; s=arc-20160816; b=L1CNGnBwFPy7gSZB1A7v+ek4QwWUzYpi+5uPYrovLMYlzfdFWhanusVQXEfAp1d1SE NnozQ6H+P5Q3XPuGjSIWIubGF5IkAJNd1P7kBGgbmGRQG+EQce6aney8/MB21tXGbj8c M4+2ZVamLBoSjnRMP1f5DBT/xm/RRb7DnFGJvQhbjZAzPiBf6EZsIsQmzrdbdHkA1e5b du1kZODpHikXRoc8af+lehSoztk8rHzdaKbeNQRPflYwuAY2LIXaGoOywCvoFzKje4fl Q9Z3TkWUuW478l53gZ4bhKBDo9dgliHQ7U+p6dZ8GnyR0L/ezGMhfIRMIm6ZtU3YWlCU /m4Q== 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-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature :arc-authentication-results; bh=Zy0b6GGsjDhaF0wMvOBPa6L+/IQEJRvq7cIe9awTme8=; b=J2Oyn+S1/F52XIaDaxsE8VDh3ydik2WMaIFasNzLZ/Q+roejc7F3BDw+5gyBcxUEOV KRCeUXqFoWOwrcr4oxIv108s00jEaM6ZkhVzLbDqX5HdP+SuMtMV0QNPRZZWTTIKeP5r nv83V6vIwqyO07celnNMh+xaVYITz1a/JzCru2VKnddB/NxcJtFFRdtBLVmyzF2NHpdK bRMwXjO3gQxd6Y+xoA1EIs5i9akwE29lwJLXzw2A+NDBTQvUwWHAAIHHsycTCT3JbcKv H1dP/saFEVanVyMuBH5RalA3rNdVHNMBB6JSiiq/5KUFgIueNjWcPrNfwfwwoagintew mEJw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=DLgoLfbV; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m185si345430pfc.278.2018.02.16.11.08.12; Fri, 16 Feb 2018 11:08:27 -0800 (PST) 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=@gmail.com header.s=20161025 header.b=DLgoLfbV; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030420AbeBPNRF (ORCPT + 99 others); Fri, 16 Feb 2018 08:17:05 -0500 Received: from mail-qk0-f178.google.com ([209.85.220.178]:37190 "EHLO mail-qk0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030316AbeBPNRD (ORCPT ); Fri, 16 Feb 2018 08:17:03 -0500 Received: by mail-qk0-f178.google.com with SMTP id c128so3694781qkb.4; Fri, 16 Feb 2018 05:17:03 -0800 (PST) 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:content-transfer-encoding:in-reply-to :user-agent; bh=Zy0b6GGsjDhaF0wMvOBPa6L+/IQEJRvq7cIe9awTme8=; b=DLgoLfbVvSJcN0dw1SCOCWul6SofDpjX5NPCkkXuWoS7uDdZtUNFu0FbqAhrf29n+1 jNFTupm0rI5B/s522Pg6Ko8wT4EbzXiOIVyye4mVP5s2MtyI9n5tYmZQmzmKXbBWyFQ4 NYldjB/u30KYsNWbmTMBTtU174bEY+QvdcfdTAIT2KxaKBUJ5oFObfW9vRJXe+LiCOom mJu6dxwtLtAEIZsl6O6/BRuvja8wXm6jPs7l/A9wqqpIeFjTjkES6FeynyTpskSTD161 hjEQ5Pd4u3yf2j/Zn2iwL+F7/Ql8TkorTVqLJhRqWSx2KyNZAQwpRBvs3DMEGSi5Dy43 c8wA== 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:content-transfer-encoding :in-reply-to:user-agent; bh=Zy0b6GGsjDhaF0wMvOBPa6L+/IQEJRvq7cIe9awTme8=; b=qFrOaxwGN90vXym+a5tjB5WQX8wI2ylFiUghK0HLTiH3I1UMoMeeXi5Js1wgmXgBgG eeUgSFCdGzW8rkcCbgf5zJvbzD3/oPap+CFNmgyStdGo3INMlGgvfVVl2+uLymI4tys9 DUC09RxjYcn3VayZeCbFVdKUggNOeDCzK1ZnkFqX3v25mgGQ0tMXYcw4AsRz9oEnKy3Q iucf4vdeLsnmYO4bf7Tk3ZJPw74skpvktvqtKTBn5mc2t8f+QVWzFBceIfGE/aDQPuRN rX0S+8QUn+b1mJPbqMy5d410PtF+NZgXGXF6+W+6p7BAYbBaHgjkuk8w5NnwVfq6Se6V d0Vg== X-Gm-Message-State: APf1xPBBfd5qzPh3fEJMmSNzbJUJ+FunTU/ZYBNuTkTZ0tM41X3GXmo1 WcPOOJTCod5YSDp3tsxPGeM= X-Received: by 10.55.76.17 with SMTP id z17mr9749527qka.145.1518787022389; Fri, 16 Feb 2018 05:17:02 -0800 (PST) Received: from smtp.gmail.com ([143.107.45.1]) by smtp.gmail.com with ESMTPSA id k63sm7403249qte.3.2018.02.16.05.16.59 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 16 Feb 2018 05:17:01 -0800 (PST) Date: Fri, 16 Feb 2018 11:16:58 -0200 From: Rodrigo Siqueira To: Daniel Baluta Cc: "lars@metafoo.de" , "knaack.h@gmx.de" , "Michael.Hennerich@analog.com" , "jic23@kernel.org" , "pmeerw@pmeerw.net" , "gregkh@linuxfoundation.org" , "linux-kernel@vger.kernel.org" , "linux-iio@vger.kernel.org" , "devel@driverdev.osuosl.org" Subject: Re: [PATCH] staging: iio/meter: add name to function definition arguments Message-ID: <20180216131658.h7b2y2ckkucetnzj@smtp.gmail.com> References: <20180216125041.qfvg7xtpulc54tk6@smtp.gmail.com> <1518785796.9517.25.camel@nxp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1518785796.9517.25.camel@nxp.com> User-Agent: NeoMutt/20171215 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Daniel > Hi Rodrigo, > > I think this is a nice finding. One comment inline: > > On Vi, 2018-02-16 at 10:50 -0200, rodrigosiqueira wrote: > > This patch fixes the checkpatch.pl warning: > > > > drivers/staging/iio/meter/ade7854.h:157: WARNING: function definition > > argument 'struct device *' should also have an identifier name... > >? > > + int (*read_reg_32)(struct device *dev, u16 reg_address, u32 *val); > > + int (*write_reg_8)(struct device *dev, u16 reg_address, u8 value); > > > Any particular reason for using val vs value? I get that one is a pointer > and another a plain type, but I think the name should be the same. Before I selected the name, I figure out that read_reg_* and write_reg_* was assigned inside the iio/meter/ade7754-(i2c|spi).c files by function like ade7754_*_read_reg_* and ade7754_*_write_reg_* . I considered to use 'value' name for both functions parameters, however, I noticed that function ade7754_*_write_reg_* adopted the name 'value' for the last argument and ade7754_*_read_reg_* named the last argument as 'val'. So, for consistency sake between the header file and the c code, I decided to use the same parameter name patterns. > thanks, > Daniel. > Thanks