Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp692328rwl; Wed, 29 Mar 2023 07:18:33 -0700 (PDT) X-Google-Smtp-Source: AKy350YQsVa51lX4TN010s96H9aD55Mp8qPGf98YD0E2wu27fXw8inq4CNPJW24P3tSgDzdaK6Wl X-Received: by 2002:a17:906:e294:b0:8b1:32b0:2a24 with SMTP id gg20-20020a170906e29400b008b132b02a24mr20321493ejb.47.1680099513525; Wed, 29 Mar 2023 07:18:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1680099513; cv=none; d=google.com; s=arc-20160816; b=RBqhsjgIPds16I5sH5InjO9Djo5Gv/nVVYKDK5GmSdAR92NnophxYuisItwMbFgnkE 6DHP6ajiRttNFteEo7iHbehhLM+l7pAVRLU4b3CW6jHW1JaPpRy9R2Zx9cbjKDorggB6 azXulLl/JE7eRBr5tJBOjVZvAQU8zaKTvyh9z+qFRm67Pikp64Iz2KORjl9JQIJAvbOa g0sKeqUHfAf41dvZpyZKMs4VRaQFgZ9mXqDP3IlZTkvsQEgbh9tcJGSMMhkJkNG8hkOx 1JKdvRSj71gAxdfpRp/H11tjn1lNi0ik5U45xWE96Yv+TQFY8zzGwtBtb2+uEv42Z9a1 Awxg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=oTVDrZf5cMzTSpS5sNgQ6zkBiPYBXnkcyQH/2P6NBM4=; b=VUuBAMT5yZCD9pZ1BeFb2EWaLDJddmERzY5eI+XUkagMQ04p0LCe+gLfTP7SGaNXW6 W06yX1KfBnD5RAPRWKngIuDLSv6gXyN7qh9YTekhybhNOvhMma6+ivH+b4E+cdN6lPxg yiNaLJ2PNMuW7PY4kexOEyiGfN6kMljWOyS8T+hXAep+sxIfFtj2wKZ8dciFhkziTk9O LdXyWHdUK1oI+JS4MBV3sJ9F7bobwmT9QjNH56R5i2tMQjwOTZuq0BNFD4tO3e8jq5tn IONp2tftJw/DH43nE24YhdGhaAXnduCTJx+SaSPzPtrFEeIjnnV1Wezi00LUUXmqk0Lz pSIw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=ksIIuM1T; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id u11-20020a170906950b00b00946a18bb2dfsi4802205ejx.986.2023.03.29.07.18.08; Wed, 29 Mar 2023 07:18:33 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=ksIIuM1T; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229814AbjC2OKo (ORCPT + 99 others); Wed, 29 Mar 2023 10:10:44 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45362 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230116AbjC2OKk (ORCPT ); Wed, 29 Mar 2023 10:10:40 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B2D8735A7; Wed, 29 Mar 2023 07:09:49 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 2A7A0B8233F; Wed, 29 Mar 2023 14:09:17 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 87B24C433EF; Wed, 29 Mar 2023 14:09:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1680098955; bh=9lynLMkfJlpl0/geEJFWUVNSLRtWY6ohBkQxzVnlj/s=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ksIIuM1TVGDnKQZDp8EN6vjridqEQSGdUgFoC8Hei1O98taVwxIya366RuoQbCnR6 Xni9pPcmfvnieMsKaCDZSye7bksr5RGFzTXz/1MlqOO9waUSlI+TrjC8t+UaEZUh57 0p8SysMAcXnSg4SiqMivHP3y4/Cu18htLpu9sQkw= Date: Wed, 29 Mar 2023 16:09:13 +0200 From: Greg Kroah-Hartman To: Conor Dooley Cc: corbet@lwn.net, conor@kernel.org, Russ Weight , Tianfei zhang , Luis Chamberlain , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] docs: driver-api: firmware_loader: fix missing argument in usage example Message-ID: References: <20230329123425.4177084-1-conor.dooley@microchip.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230329123425.4177084-1-conor.dooley@microchip.com> X-Spam-Status: No, score=-2.5 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 29, 2023 at 01:34:26PM +0100, Conor Dooley wrote: > By the time firmware-upload support landed in commit 97730bbb242c > ("firmware_loader: Add firmware-upload support"), the arguments for > firmware_upload_register() had changed, and while this is automagically > represented in the kernel doc bits, the usage example was not kept in > sync. > Add the missing argument as per the driver. > > Fixes: 97730bbb242c ("firmware_loader: Add firmware-upload support") > Signed-off-by: Conor Dooley > --- > >From skimming the threads adding this stuff, looks like THIS_MODULE was > always needed, so either I'm missing something or the doc stuff wasn't > matching in any of the submitted versions. > > CC: Jonathan Corbet > CC: Russ Weight > CC: Greg Kroah-Hartman > CC: Tianfei zhang > CC: Luis Chamberlain > CC: linux-doc@vger.kernel.org > CC: linux-kernel@vger.kernel.org > --- > Documentation/driver-api/firmware/fw_upload.rst | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/Documentation/driver-api/firmware/fw_upload.rst b/Documentation/driver-api/firmware/fw_upload.rst > index 76922591e446..edf1d0c5e7c3 100644 > --- a/Documentation/driver-api/firmware/fw_upload.rst > +++ b/Documentation/driver-api/firmware/fw_upload.rst > @@ -57,7 +57,8 @@ function calls firmware_upload_unregister() such as:: > len = (truncate) ? truncate - fw_name : strlen(fw_name); > sec->fw_name = kmemdup_nul(fw_name, len, GFP_KERNEL); > > - fwl = firmware_upload_register(sec->dev, sec->fw_name, &m10bmc_ops, sec); > + fwl = firmware_upload_register(THIS_MODULE, sec->dev, sec->fw_name, > + &m10bmc_ops, sec); Good catch. As this touches the firmware documentation, I can take it in my tree, thanks! greg k-h