From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx2.suse.de ([195.135.220.15]:48413 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751463AbeB1BVd (ORCPT ); Tue, 27 Feb 2018 20:21:33 -0500 Date: Wed, 28 Feb 2018 01:21:31 +0000 From: "Luis R. Rodriguez" To: Kees Cook Cc: "Luis R. Rodriguez" , cantabile.desu@gmail.com, Jakub Kicinski , Greg KH , Andrew Morton , linux-wireless , Shuah Khan , Martin Fuzzey , Mimi Zohar , David Howells , pali.rohar@gmail.com, Takashi Iwai , arend.vanspriel@broadcom.com, =?utf-8?B?UmFmYcWCIE1pxYJlY2tp?= , nbroeking@me.com, Vikram Mulukutla , stephen.boyd@linaro.org, Mark Brown , Dmitry Torokhov , David Woodhouse , Linus Torvalds , Abhay_Salunke@dell.com, bjorn.andersson@linaro.org, jewalt@lgsinnovations.com, oneukum@suse.com, LKML , "linux-fsdevel@vger.kernel.org" Subject: Re: [RFT 1/7] rename: _request_firmware_load() fw_load_sysfs_fallback() Message-ID: <20180228012131.GF14069@wotan.suse.de> (sfid-20180228_022146_558250_DDDB1163) References: <20180227232101.20786-1-mcgrof@kernel.org> <20180227232101.20786-2-mcgrof@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: linux-wireless-owner@vger.kernel.org List-ID: On Tue, Feb 27, 2018 at 03:28:21PM -0800, Kees Cook wrote: > On Tue, Feb 27, 2018 at 3:20 PM, Luis R. Rodriguez wrote: > > This reflects much clearer what is being done. > > > > Signed-off-by: Luis R. Rodriguez > > --- > > Documentation/driver-api/firmware/fallback-mechanisms.rst | 2 +- > > drivers/base/firmware_fallback.c | 4 ++-- > > 2 files changed, 3 insertions(+), 3 deletions(-) > > > > diff --git a/Documentation/driver-api/firmware/fallback-mechanisms.rst b/Documentation/driver-api/firmware/fallback-mechanisms.rst > > index 4055ac76b288..f353783ae0be 100644 > > --- a/Documentation/driver-api/firmware/fallback-mechanisms.rst > > +++ b/Documentation/driver-api/firmware/fallback-mechanisms.rst > > @@ -112,7 +112,7 @@ Since a device is created for the sysfs interface to help load firmware as a > > fallback mechanism userspace can be informed of the addition of the device by > > relying on kobject uevents. The addition of the device into the device > > hierarchy means the fallback mechanism for firmware loading has been initiated. > > -For details of implementation refer to _request_firmware_load(), in particular > > +For details of implementation refer to fw_load_sysfs_fallback(), in particular > > on the use of dev_set_uevent_suppress() and kobject_uevent(). > > > > The kernel's kobject uevent mechanism is implemented in lib/kobject_uevent.c, > > diff --git a/drivers/base/firmware_fallback.c b/drivers/base/firmware_fallback.c > > index 13fa5ff2b46c..ce7ccfe82c69 100644 > > --- a/drivers/base/firmware_fallback.c > > +++ b/drivers/base/firmware_fallback.c > > @@ -536,7 +536,7 @@ fw_create_instance(struct firmware *firmware, const char *fw_name, > > } > > > > /* load a firmware via user helper */ > > As long as this is being renamed, maybe add full kern-doc for this function? Sure why not. Luis