On Mon, Jul 26, 2010 at 02:49:56PM +0300, Antti Kantee wrote:
> On Sun Jul 25 2010 at 15:17:29 -0700, Paul Goyette wrote:
> > On Mon, 26 Jul 2010, matthew green wrote:
> >
> > >
> > >it seems to me the root problem is that module_mutex is held while
> > >calling into the module startup routines.
>
On Tue, Jul 27, 2010 at 09:23:04AM +0200, Martin Husemann wrote:
> On Tue, Jul 27, 2010 at 01:56:23AM +, Quentin Garnier wrote:
> > "For free" is a subjective thing. I don't think using device_register()
> > --which is a MD callback--to pass information between two MI drivers is
> > free.
>
>
On Wed, Jul 28, 2010 at 03:09:36PM +, Quentin Garnier wrote:
> On Tue, Jul 27, 2010 at 09:23:04AM +0200, Martin Husemann wrote:
> > On Tue, Jul 27, 2010 at 01:56:23AM +, Quentin Garnier wrote:
> > > "For free" is a subjective thing. I don't think using device_register()
> > > --which is a
On Wed, Jul 28, 2010 at 11:00:58AM -0500, David Young wrote:
> On Wed, Jul 28, 2010 at 03:09:36PM +, Quentin Garnier wrote:
> > On Tue, Jul 27, 2010 at 09:23:04AM +0200, Martin Husemann wrote:
[...]
> > > FWIW, what David outlines is pretty close to the way i2c direct config
> > > works in -cur
On Wed, Jul 28, 2010 at 04:41:20PM +, Quentin Garnier wrote:
> [..] My intent was to provide a new tool, and to show an
> example of a situation where said tool is less of a kludge, more module-
> friendly and so on.
Sorry to be one of the folks who don't get it, but your new tool looks
very
