[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160906222847.GF15161@tuxbot>
Date: Tue, 6 Sep 2016 15:28:47 -0700
From: Bjorn Andersson <bjorn.andersson@...aro.org>
To: "Luis R. Rodriguez" <mcgrof@...nel.org>
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
Jacek Anaszewski <j.anaszewski@...sung.com>,
David Woodhouse <dwmw2@...radead.org>,
Christian Lamparter <chunkeey@...glemail.com>,
Julia Lawall <Julia.Lawall@...6.fr>,
Andrew Morton <akpm@...ux-foundation.org>,
linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
Mimi Zohar <zohar@...ux.vnet.ibm.com>,
Andy Lutomirski <luto@...capital.net>,
Richard Purdie <rpurdie@...ys.net>,
Wu Fengguang <fengguang.wu@...el.com>,
Johannes Berg <johannes@...solutions.net>,
Michal Marek <mmarek@...e.com>,
Hauke Mehrtens <hauke@...ke-m.de>,
Mark Brown <broonie@...nel.org>, Jiri Slaby <jslaby@...e.com>,
Ming Lei <ming.lei@...onical.com>,
Daniel Vetter <daniel.vetter@...ll.ch>,
Kevin Cernekee <cernekee@...il.com>,
Jeff Mahoney <jeffm@...e.com>,
Greg KH <gregkh@...uxfoundation.org>,
Jonathan Corbet <corbet@....net>, Felix Fietkau <nbd@....name>,
David Howells <dhowells@...hat.com>,
Vikram Mulukutla <markivx@...eaurora.org>,
Alessandro Rubini <rubini@...dd.com>,
Tom Gundersen <teg@...m.no>, Kees Cook <keescook@...omium.org>,
Takashi Iwai <tiwai@...e.de>, Gilles.Muller@...6.fr,
linux-serial <linux-serial@...r.kernel.org>,
Roman Pen <r.peniaev@...il.com>, Kay Sievers <kay@...y.org>,
Stephen Boyd <stephen.boyd@...aro.org>, nicolas.palix@...g.fr,
"Abhay_Salunke@...l.com" <Abhay_Salunke@...l.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Thierry Martinez <martinez@...p.org>,
Josh Boyer <jwboyer@...oraproject.org>
Subject: Re: [RFC] fs: add userspace critical mounts event support
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
Powered by blists - more mailing lists