From: fabio.estevam@freescale.com (Fabio Estevam)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] ARM: mx5: dynamically allocate pwm devices
Date: Tue, 30 Nov 2010 12:44:27 -0200 [thread overview]
Message-ID: <4CF50DCB.5090808@freescale.com> (raw)
In-Reply-To: <20101130143837.GK20449@pengutronix.de>
Hi Uwe,
On 11/30/2010 12:38 PM, Uwe Kleine-K?nig wrote:
> Hello Fabio,
>
> both patches look ok. (Yes, that's an Acked-by: me for both)
>
> Uwe
I am working on v3 as I realized I forgot to remove the keypad entries
from devices.c and devices.h and also to use register keypad dynamically
for 2 boards (eukrea_mbimx51-baseboard and board-mx51_3ds.c).
Will submit it soon.
Thanks,
Fabio Estevam
prev parent reply other threads:[~2010-11-30 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 12:02 [PATCH v2 1/2] ARM: mx5: dynamically allocate pwm devices Fabio Estevam
2010-11-30 12:02 ` [PATCH v2 2/2] ARM: mx5: dynamically allocate imx-keypad devices Fabio Estevam
2010-11-30 14:38 ` [PATCH v2 1/2] ARM: mx5: dynamically allocate pwm devices Uwe Kleine-König
2010-11-30 14:44 ` Fabio Estevam [this message]
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=4CF50DCB.5090808@freescale.com \
--to=fabio.estevam@freescale.com \
--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).