mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "pHilipp Zabel" <philipp.zabel@gmail.com>
To: ian <spyro@f2s.com>
Cc: Dmitry <dbaryshkov@gmail.com>,
	"Samuel Ortiz" <sameo@openedhand.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Ben Dooks" <ben-linux@fluff.org>,
	"Russell King - ARM Linux" <linux@arm.linux.org.uk>
Subject: Re: [PATCH] MFD maintainer
Date: Thu, 19 Jun 2008 18:10:58 +0200	[thread overview]
Message-ID: <74d0deb30806190910w558636cat21d1ffd4b0036f51@mail.gmail.com> (raw)
In-Reply-To: <1213888192.17281.45.camel@wirenth>

On Thu, Jun 19, 2008 at 5:09 PM, ian <spyro@f2s.com> 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?

> 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

  parent reply	other threads:[~2008-06-19 16:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-18 21:42 Samuel Ortiz
2008-06-19  9:59 ` pHilipp Zabel
2008-06-19 10:54   ` ian
2008-06-19 11:12     ` Dmitry
2008-06-19 15:09       ` ian
2008-06-19 15:32         ` Dmitry
2008-06-19 16:06           ` pHilipp Zabel
2008-06-19 16:19             ` Dmitry
2008-06-19 18:30             ` ian
2008-06-19 16:10         ` pHilipp Zabel [this message]
2008-06-19 16:16           ` Dmitry

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=74d0deb30806190910w558636cat21d1ffd4b0036f51@mail.gmail.com \
    --to=philipp.zabel@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=ben-linux@fluff.org \
    --cc=dbaryshkov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=sameo@openedhand.com \
    --cc=spyro@f2s.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®