From: Samuel Ortiz <sameo@linux.intel.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "Andres Salomon" <dilinger@queued.net>,
"Sascha Hauer" <kernel@pengutronix.de>,
"Amit Kucheria" <amit.kucheria@canonical.com>,
"Russell King" <linux@arm.linux.org.uk>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: [PATCH] ARM: mx51_efika: update platform data for new mfd changes
Date: Fri, 11 Mar 2011 21:44:05 +0100 [thread overview]
Message-ID: <20110311204405.GE20247@sortiz-mobl> (raw)
In-Reply-To: <20110307085358.GM29521@pengutronix.de>
Hi Sascha,
On Mon, Mar 07, 2011 at 09:53:58AM +0100, Sascha Hauer wrote:
> On Fri, Mar 04, 2011 at 08:06:53AM -0800, Andres Salomon wrote:
> > Note that this relies on stuff currently in mfd's next tree, but this
> > is also a newer driver. I'm not sure which tree it should go through,
> > as it's a problem that shows up in next.
>
> Please ping me again when the mfd tree is in Linus master. I see no
> other chance fixing this on my side other than removing regulator
> support for efika completely for now. So I guess you have to live with
> the compile breakage for some time.
It would probably make sense for me to carry this driver then. Sascha, would
you be ok with it ? If that's so, could you please point me at a git commit
from your tree ?
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
WARNING: multiple messages have this Message-ID (diff)
From: sameo@linux.intel.com (Samuel Ortiz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mx51_efika: update platform data for new mfd changes
Date: Fri, 11 Mar 2011 21:44:05 +0100 [thread overview]
Message-ID: <20110311204405.GE20247@sortiz-mobl> (raw)
In-Reply-To: <20110307085358.GM29521@pengutronix.de>
Hi Sascha,
On Mon, Mar 07, 2011 at 09:53:58AM +0100, Sascha Hauer wrote:
> On Fri, Mar 04, 2011 at 08:06:53AM -0800, Andres Salomon wrote:
> > Note that this relies on stuff currently in mfd's next tree, but this
> > is also a newer driver. I'm not sure which tree it should go through,
> > as it's a problem that shows up in next.
>
> Please ping me again when the mfd tree is in Linus master. I see no
> other chance fixing this on my side other than removing regulator
> support for efika completely for now. So I guess you have to live with
> the compile breakage for some time.
It would probably make sense for me to carry this driver then. Sascha, would
you be ok with it ? If that's so, could you please point me at a git commit
from your tree ?
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2011-03-11 20:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 16:06 [PATCH] ARM: mx51_efika: update platform data for new mfd changes Andres Salomon
2011-03-04 16:06 ` Andres Salomon
2011-03-04 16:14 ` Sergei Shtylyov
2011-03-04 16:14 ` Sergei Shtylyov
2011-03-04 16:38 ` Andres Salomon
2011-03-04 16:38 ` Andres Salomon
2011-03-04 18:58 ` Sergei Shtylyov
2011-03-04 18:58 ` Sergei Shtylyov
2011-03-07 14:47 ` Mark Brown
2011-03-07 14:47 ` Mark Brown
2011-03-08 5:32 ` Andres Salomon
2011-03-08 5:32 ` Andres Salomon
2011-03-04 19:46 ` Uwe Kleine-König
2011-03-04 19:46 ` Uwe Kleine-König
2011-03-07 8:53 ` Sascha Hauer
2011-03-07 8:53 ` Sascha Hauer
2011-03-11 20:44 ` Samuel Ortiz [this message]
2011-03-11 20:44 ` Samuel Ortiz
2011-03-15 8:33 ` Sascha Hauer
2011-03-15 8:33 ` Sascha Hauer
2011-03-24 20:27 ` Andres Salomon
2011-03-24 20:27 ` Andres Salomon
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=20110311204405.GE20247@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=amit.kucheria@canonical.com \
--cc=dilinger@queued.net \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=s.hauer@pengutronix.de \
--cc=sfr@canb.auug.org.au \
--cc=u.kleine-koenig@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.