From: jaume@fqingenieria.es (Jaume Ribot)
To: linux-arm-kernel@lists.infradead.org
Subject: MX25 patches
Date: Tue, 23 Nov 2010 10:51:31 +0100 [thread overview]
Message-ID: <4CEB8EA3.7000608@fqingenieria.es> (raw)
In-Reply-To: <20101119083827.GD6017@pengutronix.de>
Dear Sascha,
We are also working on some patches for I.MX25. As we have seen some
significant modifications in Uwe's git (specially regarding file
locations), maybe it's better to wait for this patches when merged with
to your repository?
Jaume
On 19/11/2010 9:38, Sascha Hauer wrote:
> On Thu, Nov 18, 2010 at 07:54:39PM +0800, Richard Zhao wrote:
>> Hi Sascha,
>>
>> Is branch imx-for-2.6.38 the latest branch for arch/arm/mach-mx5? I'm
>> preparing mx50 reference design board support.
> Yes, but there are Uwes latest patches pending. I don't know if they
> conflict with what you want to do.
>
> Sascha
>
>
next prev parent reply other threads:[~2010-11-23 9:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 18:35 [PATCH 0/5] mx51: Add PWM support Fabio Estevam
2010-11-18 10:25 ` Sascha Hauer
2010-11-18 11:54 ` Richard Zhao
2010-11-19 8:38 ` Sascha Hauer
2010-11-23 9:51 ` Jaume Ribot [this message]
2010-11-25 9:01 ` MX25 patches Sascha Hauer
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=4CEB8EA3.7000608@fqingenieria.es \
--to=jaume@fqingenieria.es \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).