[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121023132939.GA10160@opensource.wolfsonmicro.com>
Date: Tue, 23 Oct 2012 14:29:39 +0100
From: Dimitris Papastamos <dp@...nsource.wolfsonmicro.com>
To: Ming Lei <tom.leiming@...il.com>
Cc: linux-kernel@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH 1/3 v2] firmware: Convert firmware path setup from an
array to a list
On Tue, Oct 23, 2012 at 09:08:50PM +0800, Ming Lei wrote:
> On Tue, Oct 23, 2012 at 8:52 PM, Dimitris Papastamos
> <dp@...nsource.wolfsonmicro.com> 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
> firmware via procfs, looks you don't reply, :-(
>
> http://marc.info/?l=linux-kernel&m=134988208617179&w=2
>
> IMO, it is not a good idea to update firmware path dynamically via proc
> because it may be too late to update a dynamic search path via /proc
> and drivers need request firmware just after rootfs is mounted.
>
> kernel parameter should be a good way to pass one customerized
> path.
>
> Thanks,
> --
> Ming Lei
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.
Should I amend the commit description so it is not misleading and
remove the 'updating' part?
Thanks,
Dimitris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists