Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp6866824ybi; Wed, 31 Jul 2019 23:20:28 -0700 (PDT) X-Google-Smtp-Source: APXvYqyb65nmyOrTrSULF2qkqzSR/RFQafk6FxhIkJc9ZJAaObaWs/n8cNSAReZ/UmG/vNRD+GzH X-Received: by 2002:a65:5c4b:: with SMTP id v11mr74824920pgr.62.1564640427851; Wed, 31 Jul 2019 23:20:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1564640427; cv=none; d=google.com; s=arc-20160816; b=nxC+HHGsyoD5uOpkeNF3pUDEyaE0MbUiTSwh+v68RyQeKg+vvbSP0kamgdXtsMikmP zoRJUAjghw/Ap6LmAyrb9VJ6fAyG/6J1vyAoriW/0g5QLD0MexOZLeAs9rutNPockk8h RISJ1PSB3cSyuAgD5cPmRBOj+AjEnRr6ovXWe2PzkA/6DKOjHq3BpJInR4BusrKqDEcE NcLZb8Aag4n5eCwYyb2wUIyzYPgG9OYKOKov7HIVQlPAnTvrc5pmyiYH7RpVmYvgQ4Ek bG+HwYMQv+UYO//tbgXyXKurenTztlXJGw9ImvydJ4jpMmSBq1UrnCC0CrnEiyMdRrqm Cr+g== 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; bh=HrRiVrtRnUr5bwx7jZBw/CEn9BBsKRflbjzHBvAmvws=; b=DzCqSSZCICfTwxXXhg17sQ+LNKImoCxb6fi7vzGFx7XG3SKf/YdL91iT/+cfuOprDx GnyYnhlerz58w4rwMtSYqekTiQldvdU4r1yjKwMibJQy4t2DfCTpvGVJZ2HB5tD2LhYg zjpYciA+BXatdjatLtRYhi7GO4ChEZ/0McQnfmspneTJyEE+qUs2UZ+GrFPDyC0/Z8kv R/rYU2aHTrEbReIaRmSASspS5ALUrUnFZAQvkLI6Ypv5J6brmqIFG2s1lw8dRAXshScN 0mIjBhY+KxBg9iceFABSQvTJxP/nPWgJCzjXfOjA1stEamNQDyEL3A+EEAYUT5nc5nmp 7kjw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=Gpc+lB55; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u128si29094454pgu.389.2019.07.31.23.20.11; Wed, 31 Jul 2019 23:20:27 -0700 (PDT) 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=@kernel.org header.s=default header.b=Gpc+lB55; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729846AbfHAGSF (ORCPT + 99 others); Thu, 1 Aug 2019 02:18:05 -0400 Received: from mail.kernel.org ([198.145.29.99]:57506 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728884AbfHAGSE (ORCPT ); Thu, 1 Aug 2019 02:18:04 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 6EDBC206A3; Thu, 1 Aug 2019 06:18:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1564640283; bh=P7+ACBH9J5mTnDheikQW7WOAS+HoMLWPjzJygxs6sMA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Gpc+lB55+mtiUztM8rfj9Me584E3lPqEIfzL0dMJfaRla1hs1CZsZz7iQFjdiJzfU wv3d8zKZ0NSuxjK/IRpQBTGnJ0OeSpcIxKFpWFtpY99JupeJ93Ba0skNlYsMOJewoz yc5sOggjdNqt405T59V7d9QAnkynqcHVMmi05D0s= Date: Thu, 1 Aug 2019 08:18:01 +0200 From: Greg Kroah-Hartman To: Scott Branden Cc: Luis Chamberlain , David Brown , Alexander Viro , "Rafael J . Wysocki" , linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-fsdevel@vger.kernel.org, BCM Kernel Feedback , Olof Johansson Subject: Re: [PATCH 2/3] firmware: add offset to request_firmware_into_buf Message-ID: <20190801061801.GA4338@kroah.com> References: <20190523025113.4605-1-scott.branden@broadcom.com> <20190523025113.4605-3-scott.branden@broadcom.com> <20190523055233.GB22946@kroah.com> <15c47e4d-e70d-26bb-9747-0ad0aa81597b@broadcom.com> <20190523165424.GA21048@kroah.com> <44282070-ddaf-3afb-9bdc-4751e3f197ac@broadcom.com> <20190524052258.GB28229@kroah.com> <2f67db0a-27c3-d13c-bbe0-0af5edd4f0da@broadcom.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <2f67db0a-27c3-d13c-bbe0-0af5edd4f0da@broadcom.com> User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 31, 2019 at 05:18:32PM -0700, Scott Branden wrote: > Hi Greg, > > I am now back from leave to continue this patch.? Comment below. > > On 2019-05-23 10:22 p.m., Greg Kroah-Hartman wrote: > > On Thu, May 23, 2019 at 10:01:38PM -0700, Scott Branden wrote: > > > On 2019-05-23 9:54 a.m., Greg Kroah-Hartman wrote: > > > > On Thu, May 23, 2019 at 09:36:02AM -0700, Scott Branden wrote: > > > > > Hi Greg, > > > > > > > > > > On 2019-05-22 10:52 p.m., Greg Kroah-Hartman wrote: > > > > > > On Wed, May 22, 2019 at 07:51:12PM -0700, Scott Branden wrote: > > > > > > > Add offset to request_firmware_into_buf to allow for portions > > > > > > > of firmware file to be read into a buffer. Necessary where firmware > > > > > > > needs to be loaded in portions from file in memory constrained systems. > > > > > > > > > > > > > > Signed-off-by: Scott Branden > > > > > > > --- > > > > > > > drivers/base/firmware_loader/firmware.h | 5 +++ > > > > > > > drivers/base/firmware_loader/main.c | 49 +++++++++++++++++-------- > > > > > > > include/linux/firmware.h | 8 +++- > > > > > > > 3 files changed, 45 insertions(+), 17 deletions(-) > > > > > > No new firmware test for this new option? How do we know it even works? > > > > > I was unaware there are existing firmware tests.? Please let me know where > > > > > these tests exists and I can add a test for this new option. > > > > tools/testing/selftests/firmware/ > > > Unfortunately, there doesn't seem to be a test for the existing > > > request_firmware_into_buf api. > > Are you sure? The test is for userspace functionality, there isn't > > kernel unit tests here. You need to verify that you didn't break > > existing functionality as well as verify that your new functionality > > works. > > I managed to figure out how to build and run > tools/testing/selftest/firmware/fw_run_tests.sh > > and my changes don't break existing functionality. > > But, I find no use of request_firmware_into_buf in lib/test_firmware.c > (triggered by fw_run_tests.sh). > > Is there another test for request_firmware_into_buf? I have no idea, sorry. greg k-h