[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080709210314.GF26734@flint.arm.linux.org.uk>
Date: Wed, 9 Jul 2008 22:03:14 +0100
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: Dmitry <dbaryshkov@...il.com>
Cc: ian <spyro@....com>, linux-kernel@...r.kernel.org,
Ben Dooks <ben-linux@...ff.org>,
linux-arm-kernel@...ts.arm.linux.org.uk
Subject: Re: [patch 4/4] MFD: Change mfd platform device usage to wrapper platform_device
On Wed, Jul 09, 2008 at 03:52:08PM +0400, Dmitry wrote:
> 2008/7/9 ian <spyro@....com>:
> > On Wed, 2008-07-09 at 15:15 +0400, Dmitry wrote:
> >> NAK.
> >> 0) It was discussed yesterday on the list and the decision was to go
> >> in a different way.
> >
> > It was?
> >
> > I prefer the wrapped way personally...
>
> In any case IMO it's better to call platform_device_register() rather than
> device_initialise()/platform_device_add().
>
> Samuel? Russell?
WTF??? That's just completely wrong - assuming the internals of how the
platform device alloc API works...
What it's clear from my *brief* read of this thread is that the MFD
support doesn't seem to be ready for mainline yet - there's clearly issues
here that need further work.
Given that, and where we are (there's maybe two of *my* days left until
the merge window opens) I'm *very* tempted to drop the MFD support out
of my tree for this merge window - which basically means removing
5127/1, 5128/1 and 5129/1.
--
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