Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751922AbdF0GxF (ORCPT ); Tue, 27 Jun 2017 02:53:05 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:45794 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751492AbdF0GxA (ORCPT ); Tue, 27 Jun 2017 02:53:00 -0400 Date: Tue, 27 Jun 2017 08:52:53 +0200 From: Greg Kroah-Hartman To: Bjorn Andersson Cc: "Luis R. Rodriguez" , Daniel Wagner , David Woodhouse , rafal@milecki.pl, Arend van Spriel , "Rafael J. Wysocki" , yi1.li@linux.intel.com, atull@opensource.altera.com, Moritz Fischer , pmladek@suse.com, Johannes Berg , emmanuel.grumbach@intel.com, luciano.coelho@intel.com, Kalle Valo , luto@kernel.org, Linus Torvalds , Kees Cook , "AKASHI, Takahiro" , David Howells , pjones@redhat.com, Hans de Goede , alan@linux.intel.com, tytso@mit.edu, lkml Subject: Re: [PATCH] firmware: remove request_firmware_into_buf() Message-ID: <20170627065253.GB29909@kroah.com> References: <20170623160321.GA19720@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.3 (2017-05-23) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1289 Lines: 31 On Mon, Jun 26, 2017 at 01:22:41PM -0700, Bjorn Andersson wrote: > On Fri, Jun 23, 2017 at 9:03 AM, Greg Kroah-Hartman > wrote: > > As Luis pointed out, there are no in-kernel users of > > request_firmware_into_buf(), so remove it, and the now unused internal > > flag, which simplifies the logic around buffer handling a bit. > > > > This API was implemented to reduce the memory pressure during firmware > load in the Qualcomm remoteprocs, but it wasn't available when I > upstreamed that code and I apparently forgot to send out the patch > moving us over to use this API... > > Especially when loading the Qualcomm modem we have a couple of files > that we request_firmware() that are 10-15MB in size, so this > functionality is definitely wanted. > > > As we are calling release_firmware() immediately following the > request_firmware() I did attempt to just call > kernel_read_file_from_path() directly, but as I don't have access to > the fw_path[] this becomes inconsistent, so I would like to keep > request_firmware_into_buf(). Why would we keep it if there is no in-tree user for it? If you want it sometime in the future, great, we can revert the deletion then, but keeping it around for nothing isn't ok, you know that :) thanks, greg k-h