Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753506AbdFSHdv (ORCPT ); Mon, 19 Jun 2017 03:33:51 -0400 Received: from s3.sipsolutions.net ([5.9.151.49]:41550 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751089AbdFSHdu (ORCPT ); Mon, 19 Jun 2017 03:33:50 -0400 Message-ID: <1497857596.2259.3.camel@sipsolutions.net> Subject: Re: [PATCH v9 1/5] firmware: add extensible driver data params From: Johannes Berg To: Greg KH , "Luis R. Rodriguez" Cc: wagi@monom.org, dwmw2@infradead.org, rafal@milecki.pl, arend.vanspriel@broadcom.com, rjw@rjwysocki.net, yi1.li@linux.intel.com, atull@opensource.altera.com, moritz.fischer@ettus.com, pmladek@suse.com, emmanuel.grumbach@intel.com, luciano.coelho@intel.com, kvalo@codeaurora.org, luto@kernel.org, torvalds@linux-foundation.org, keescook@chromium.org, takahiro.akashi@linaro.org, dhowells@redhat.com, pjones@redhat.com, hdegoede@redhat.com, alan@linux.intel.com, tytso@mit.edu, linux-kernel@vger.kernel.org Date: Mon, 19 Jun 2017 09:33:16 +0200 In-Reply-To: <20170617193815.GI2974@kroah.com> References: <20170605213314.GR8951@wotan.suse.de> <20170605213937.26215-1-mcgrof@kernel.org> <20170605213937.26215-2-mcgrof@kernel.org> <20170613090548.GA31421@kroah.com> <20170613194011.GI27288@wotan.suse.de> <20170617193815.GI2974@kroah.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6-1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 607 Lines: 15 On Sat, 2017-06-17 at 21:38 +0200, Greg KH wrote: > But we don't accept kernel patches for some mythical future option > that might be happening some time in the future.  Heck, I'm still not > convinced that firmware signing isn't anything more than just some > snakeoil in the first place! I for one really want the "firmware" signing, because I want to load the regulatory database through this API, and But honestly, I've been waiting for years for that now and started looking at what it would take to hand-implement that on top of the existing firmware API. Probably not all that much. johannes