On Tue, Oct 23, 2012 at 9:44 PM, Dimitris Papastamos
wrote:
>
> I don't currently have a use-case for this, so not sure how useful
> it is to list the default fw paths.
OK, got it, thanks for your effort.
Greg, so could we just hold on until it is useful?
Thanks,
--
Ming Lei
--
To unsubscribe
On Tue, Oct 23, 2012 at 09:37:24PM +0800, Ming Lei wrote:
> On Tue, Oct 23, 2012 at 9:29 PM, Dimitris Papastamos
> wrote:
>
> >
> > Hi sorry for being unclear, I mentioned in the old thread that
> > I've not had time to fix this properly (or think about a proper
> > fix), Greg requested a rebase
On Tue, Oct 23, 2012 at 9:29 PM, Dimitris Papastamos
wrote:
>
> Hi sorry for being unclear, I mentioned in the old thread that
> I've not had time to fix this properly (or think about a proper
> fix), Greg requested a rebase on top of linux-next, however, at
> least for firmware path listing.
>
>
On Tue, Oct 23, 2012 at 09:08:50PM +0800, Ming Lei wrote:
> On Tue, Oct 23, 2012 at 8:52 PM, Dimitris Papastamos
> wrote:
> > In preparation to support dynamic listing/updating of firmware
> > paths via procfs, this patch converts the firmware path configuration
> > from an array to a list.
>
> I
On Tue, Oct 23, 2012 at 8:52 PM, Dimitris Papastamos
wrote:
> In preparation to support dynamic listing/updating of firmware
> paths via procfs, this patch converts the firmware path configuration
> from an array to a list.
I remembered that I have questioned on dynamic listing/updating of
firmwa
In preparation to support dynamic listing/updating of firmware
paths via procfs, this patch converts the firmware path configuration
from an array to a list.
Signed-off-by: Dimitris Papastamos
---
drivers/base/firmware_class.c | 74 +--
1 file changed, 65
6 matches
Mail list logo
