From: ian <spyro@f2s.com>
To: pHilipp Zabel <philipp.zabel@gmail.com>
Cc: Samuel Ortiz <sameo@openedhand.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ben Dooks <ben-linux@fluff.org>,
Dmitry Baryshkov <dbaryshkov@gmail.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>
Subject: Re: [PATCH] MFD maintainer
Date: Thu, 19 Jun 2008 11:54:41 +0100 [thread overview]
Message-ID: <1213872881.17281.32.camel@wirenth> (raw)
In-Reply-To: <74d0deb30806190259l2ff7931fo819ededc7aec02f7@mail.gmail.com>
Hi guys!
Good timing! I just sat down with the e-series code last night!
I'd like to see the MFD core make it into mainline, and then we can
start pushing the TMIO drivers too.
These drivers are in a LOT of handhelds and I'd really like to see the
code move to mainline now.
The code is maturing well - I just bumped all the eseries stuff, which
includes the core MFD code and all the TMIO drivers from 2.6.24 to
2.6.26-git and the only issue was some minor #include breakage.
I'll tidy up the code and pop a branch on my git server for people to
review, if thats what people want.
Dmitry - if you have any pending patches now is the time to send them on
over ;-)
-Ian
On Thu, 2008-06-19 at 11:59 +0200, pHilipp Zabel wrote:
> Added Ian, Dmitry and Russell to Cc.
>
> On Wed, Jun 18, 2008 at 11:42 PM, Samuel Ortiz <sameo@openedhand.com> wrote:
> > Hi,
> >
> > We probably need someone to look after the few drivers/mfd patches coming
> > every now and then. As agreed with Andrew, I'm ok to do so and my employer
> > is fine with me spending a few working hours on it, if needed.
>
> Right now quite some of the MFD patches go through arm-kernel, but I
> guess once that initial rush of ARM machine patches depending on MFD
> patches submitted at the same time is over, it's a very good idea to
> have a proper path into the kernel.
next prev parent reply other threads:[~2008-06-19 10:56 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 [this message]
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
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=1213872881.17281.32.camel@wirenth \
--to=spyro@f2s.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=philipp.zabel@gmail.com \
--cc=sameo@openedhand.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®