Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp3046729ybt; Mon, 29 Jun 2020 13:51:34 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxTFq5SyHhFfCil077zWlwCTiDYowvr+iYulRfQh13gxc+1VHNAI+FmtOZ3tS3y/7wrJZgz X-Received: by 2002:a17:906:dbe5:: with SMTP id yd5mr15782946ejb.328.1593463893930; Mon, 29 Jun 2020 13:51:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1593463893; cv=none; d=google.com; s=arc-20160816; b=QqI7CNE7aiDr3UkpkkuW6+cpIO/2cxqY2t+ALZP71Ten0LQeM4nZP2Fr4JJxfUJ02o m2tUxi2VOL40+kcz8KiEFYxrF+Uj4vnz6RYap9slbcpUfoVj63sOmpGTrEVJUJh+5ksT +n98qDzTRK9MjkukN8tmWG7ZVbH3DUuFNm4Ox4IMBMLkzFEUwIfTwChL934oKqxGaZIw JKjIBg2BRg47JDXVAUmeGvgfgnbtTrlGB1NxPAkdIsZba804+XHX0Z54yUfqY9mTJ5Vo g9zApLeDJ5oQU0Ps9uzQwqlgBLuIm/WN2uy66VNQuENSTm7FGOBmxVUVDsNQG4o+9PWC BFXQ== 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-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=buEQVHi4pYkYNi5xR5+kq0TuOVW4rWY7G/qVT+msh3E=; b=vU1jKllojgz9PzEhnJhHBjK22wIpLHKjoRfMF93p9oE4KnodqDyDB4SxYQvxyD8xA4 xKcRAm7ihX/CB8UWhRYAdVwqurbWsWyanRcUhypDiTz9Pucd/gqWuiGsBg+Ign5tdfEJ bvqi0qEEpoD9Lt1H8fMCX9DWYRvlqR/zBImCSwz1V0bDCXrIneTPPJvV9G+nWdd2E2Ry nS5KDDlkSiBzYrBSc0XmIieoloKtQUd0xSkVms67KPMJd8fugLa2tuK8re29jmuY9aX4 Gf3umyS/RuRd0YizPkuMnxNt5EEa8NSE1kynSvyspIJTsMJlR8X7GhplHfQiP+GoR/2v vr5A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=CHK622U1; 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=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id u18si353664edx.489.2020.06.29.13.51.10; Mon, 29 Jun 2020 13:51:33 -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=@linaro.org header.s=google header.b=CHK622U1; 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=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1733082AbgF2UuL (ORCPT + 99 others); Mon, 29 Jun 2020 16:50:11 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43360 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731430AbgF2TNh (ORCPT ); Mon, 29 Jun 2020 15:13:37 -0400 Received: from mail-wr1-x444.google.com (mail-wr1-x444.google.com [IPv6:2a00:1450:4864:20::444]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 32C0CC008759 for ; Mon, 29 Jun 2020 01:47:03 -0700 (PDT) Received: by mail-wr1-x444.google.com with SMTP id k6so15681957wrn.3 for ; Mon, 29 Jun 2020 01:47:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=buEQVHi4pYkYNi5xR5+kq0TuOVW4rWY7G/qVT+msh3E=; b=CHK622U1BVBtpIrk5fAZb9epzcn8u+EYAoOwW9EKuHtj3CnEYWctFHBkGa+CdPTx7U jEzR0bJBVp/+IRiDk1elxRlwcZgYuXAtj4v7XKjXobEORe+ppJIZ9z0M5CCibHMkXvLJ BspjreQUVgczs1OCbvG73J0zXVXrd4OCoZ5d5+ciCL5ys7zkADOCMezlXYMxdrh48B/4 VnV/Xy33royF/SH39pMdpvokXsGHrjKRq0b/hQXHM6A/c1PJ2K7BEJbOWx/qmkmfN29H 1jMDcocpaT8rLEmUVHbKvS+LX1IzFj/MuI9XaAj+TN+f2uyDdU2VUEkU/ntcZytpj4Nl xhgg== 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; bh=buEQVHi4pYkYNi5xR5+kq0TuOVW4rWY7G/qVT+msh3E=; b=e088zRqcfOFcmMq0/d1cNgEqschNo071FBAkZL83a0cZabaVk/O20e3pA3IKqKVxGY njXmEWdzR+slXkT2/o7EK54LtUtQAq7VGbB1cTrT4LTpH6OkEqgUddikxIt/241XnXVN ozzgyaHoeDPoKx1PIrD8iUxsDbBTR9S82f2fjQqVkEqYBCbnY3yWzZXNV/rKkJ9eRYRb 37AcyAGJVRb4DYyo9IC26NKC8R+ruj2h7UhB2nK4/6X9vbfAQB35zClGSOQgSXwXEqHK hWvGqulpBqJAeWB2xek9x+CJQa2lUv0HMAZdqJBTuvH5gJOZ8luu9qBOjxZEfHIMz1oq PT1A== X-Gm-Message-State: AOAM533y0gWbpC3fJBELrNqVILqur7JOCpNWTpxdVYnrH8LOrY+OIzpn /wfYXbIx0tV1t7TRLEPdFaCRfw== X-Received: by 2002:a5d:6746:: with SMTP id l6mr16093673wrw.346.1593420421939; Mon, 29 Jun 2020 01:47:01 -0700 (PDT) Received: from dell ([2.27.35.144]) by smtp.gmail.com with ESMTPSA id b62sm17113004wmh.38.2020.06.29.01.47.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 29 Jun 2020 01:47:01 -0700 (PDT) Date: Mon, 29 Jun 2020 09:46:59 +0100 From: Lee Jones To: Wolfram Sang Cc: arnd@arndb.de, gregkh@linuxfoundation.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 06/10] misc: eeprom: eeprom_93cx6: Repair function arg descriptions Message-ID: <20200629084659.GI177734@dell> References: <20200626130525.389469-1-lee.jones@linaro.org> <20200626130525.389469-7-lee.jones@linaro.org> <20200627203357.GA954@ninjato> <20200629081436.GH177734@dell> <20200629082037.GA1063@kunai> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20200629082037.GA1063@kunai> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 29 Jun 2020, Wolfram Sang wrote: > > > > > @@ -270,7 +270,7 @@ EXPORT_SYMBOL_GPL(eeprom_93cx6_readb); > > > > * @eeprom: Pointer to eeprom structure > > > > * @byte: Index from where we should start reading > > > > * @data: target pointer where the information will have to be stored > > > > - * @words: Number of bytes that should be read. > > > > + * @bytes: Number of bytes that should be read. > > > > > > Now we have 'byte' and 'bytes' here as arguments which is confusing. I > > > think renaming 'words' into 'num_bytes' would be even better. > > > > I await your patch with bated breath. :) > > ? You are touching it already, why a second patch? Because it's a different change. One that's orthogonal to this set, which is designed simply to ensure the documentation matches reality. The author decided on this (less than ideal [in our humble opinion]) nomenclature from the function's inception back in 2013. Maybe there are good reasons for it to be this way. Either way, it might require a dialogue. For this set I'd rather stick to the script. That said, I genuinely don't mind drafting a patch to fix this. If I am to do so, it would also be as part as a subsequent effort. You or me - your call. Happy either way. -- Lee Jones [李琼斯] Senior Technical Lead - Developer Services Linaro.org │ Open source software for Arm SoCs Follow Linaro: Facebook | Twitter | Blog