Re: [PATCH] MFD maintainer

From: Dmitry
Date: Thu Jun 19 2008 - 12:17:11 EST


Hi,

2008/6/19 pHilipp Zabel <philipp.zabel@xxxxxxxxx>:
> On Thu, Jun 19, 2008 at 5:09 PM, ian <spyro@xxxxxxx> wrote:
>> On Thu, 2008-06-19 at 15:12 +0400, Dmitry wrote:
>>
>>> > I'll tidy up the code and pop a branch on my git server for people to
>>> > review, if thats what people want.
>>>
>>> It's better to send patches to some ML.
>>
>> Well, the code I had is updated to match linus -git branch
>> eseries_release7 if anyones curious. (no real changes since last time
>> though)
>>
>>> > Dmitry - if you have any pending patches now is the time to send them on
>>> > over ;-)
>>>
>>> Actually the code I'm using has diverged a bit from the last code I've
>>> sent before this merging pulse.
>>
>> All progress is good :)
>>
>>> As you have seen, I've tried to submit parts of the core and tmio-nand
>>> driver as a start.
>>
>> Has any of that got merged yet? If so, I'll adapt my strategy to match
>> that, otherwise I'll try to keep all the drivers in parallel.
>>
>>> Then I'd suggest to merge other tmio core bits (support for tc6387xb
>>> and t7l66xb). The MMC, usb and fb cell drivers could benefit from
>>> clocklib patches I'm trying to get in.
>>
>> I'd like to see those. I'll get MMC and USB updated ASAP.
>
> That is interesting. I just asked Samuel about the ASIC3 MMC code
> which Aric copied from tc6393xb. It seems we should try to reuse the
> tmio driver itself for ASIC3?

That was also one of the goals for the tmio cell drivers. However merging
ASIC3 support will require some hacking around address shifts for the cell.

>
>> have you solved the clock-api-tied-to-platform-architecture problem ?
>>
>>> I'll submit the updated version of mfd-core patch this evening,
>>
>> Looking forward to it.
>>
>>> however some other bits will require more time from my side.
>>
>> Lets rock :-)
>
> regards
> Philipp
>



--
With best wishes
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/