From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934564AbcIFW24 (ORCPT ); Tue, 6 Sep 2016 18:28:56 -0400 Received: from mail-pf0-f173.google.com ([209.85.192.173]:34011 "EHLO mail-pf0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933062AbcIFW2y (ORCPT ); Tue, 6 Sep 2016 18:28:54 -0400 Date: Tue, 6 Sep 2016 15:28:47 -0700 From: Bjorn Andersson To: "Luis R. Rodriguez" Cc: Dmitry Torokhov , Linus Torvalds , "open list:DOCUMENTATION" , Jacek Anaszewski , David Woodhouse , Christian Lamparter , Julia Lawall , Andrew Morton , linuxppc-dev , Mimi Zohar , Andy Lutomirski , Richard Purdie , Wu Fengguang , Johannes Berg , Michal Marek , Hauke Mehrtens , Mark Brown , Jiri Slaby , Ming Lei , Daniel Vetter , Kevin Cernekee , Jeff Mahoney , Greg KH , Jonathan Corbet , Felix Fietkau , David Howells , Vikram Mulukutla , Alessandro Rubini , Tom Gundersen , Kees Cook , Takashi Iwai , Gilles.Muller@lip6.fr, linux-serial , Roman Pen , Kay Sievers , Stephen Boyd , nicolas.palix@imag.fr, "Abhay_Salunke@dell.com" , Linux Kernel Mailing List , Thierry Martinez , Josh Boyer Subject: Re: [RFC] fs: add userspace critical mounts event support Message-ID: <20160906222847.GF15161@tuxbot> References: <20160825194133.GC3296@wotan.suse.de> <20160902235916.GO3296@wotan.suse.de> <20160903002014.GP3296@wotan.suse.de> <20160903174939.GB32345@dtor-ws> <20160906215204.GR3296@wotan.suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160906215204.GR3296@wotan.suse.de> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue 06 Sep 14:52 PDT 2016, Luis R. Rodriguez wrote: > We already have MODULE_FIRMWARE(), we could have MODULE_FIRMWARE_REQ() or > something like it to help annotate the the driver was only functional with the > firmware, punt things to kmod to deal with the requirements. That implies that a single driver will only use a single version of the firmware. There are cases where we want a single driver to load firmware depending on e.g. hardware revisions, or previous firmware version and there are cases where we want to load firmware based on requested use-cases. Regards, Bjorn