[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110926152634.GN2946@opensource.wolfsonmicro.com>
Date: Mon, 26 Sep 2011 16:26:34 +0100
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Russell King - ARM Linux <linux@....linux.org.uk>
Cc: Grant Likely <grant.likely@...retlab.ca>,
Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <greg@...ah.com>,
linux-kernel@...r.kernel.org,
Manjunath GKondaiah <manjunath.gkondaiah@...aro.org>,
Dilan Lee <dilee@...dia.com>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [RFC PATCH v3] drivercore: Add driver probe deferral mechanism
On Mon, Sep 26, 2011 at 04:12:10PM +0100, Russell King - ARM Linux wrote:
> On Mon, Sep 26, 2011 at 03:16:43PM +0100, Mark Brown wrote:
> > used but it's not a blocker for anything. Devices doing this would need
> > some way to figure out if they should -EBUSY or fail otherwise.
> Just to avoid confusion - ITYM -EAGAIN there. -EBUSY is already used
> by drivers to mean "someone else claimed a resource I need" be it the
> IO region or an IRQ resource...
Yes, I do - sorry.
--
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