From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
"Gadiyar, Anand" <gadiyar@ti.com>
Subject: Re: [PATCH 0/2] Combine zoom board-files
Date: Fri, 5 Nov 2010 14:43:58 -0700 [thread overview]
Message-ID: <20101105214358.GX9264@atomide.com> (raw)
In-Reply-To: <20101104123345.GA1952@legolas.emea.dhcp.ti.com>
* Felipe Balbi <balbi@ti.com> [101104 05:24]:
> Hi,
>
> On Wed, Oct 20, 2010 at 01:25:10AM -0500, Balbi, Felipe wrote:
> >Those boards are so similar that they don't
> >deserve separate board files.
> >
> >Felipe Balbi (2):
> > arm: omap: combine zoom2 and zoom3 board-files
> > arm: omap: zoom: substitute gpio number with symbolic name
>
> a gentle ping on these two patches. Here are patchwork links:
>
> [1] https://patchwork.kernel.org/patch/267491/
> [2] https://patchwork.kernel.org/patch/267501/
>
> they are also rebased on top of today's l-o and compile tested with
> omap2plus_defconfig, attached to this mail.
Looks good to me, but please can you please repost with also
linux-arm-kernel list Cc'd? That way I don't have to repost
before merging.
Regards,
Tony
next prev parent reply other threads:[~2010-11-05 21:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 6:25 [PATCH 0/2] Combine zoom board-files Felipe Balbi
2010-10-20 6:25 ` [PATCH 1/2] arm: omap: combine zoom2 and zoom3 board-files Felipe Balbi
2010-10-20 16:30 ` Tony Lindgren
2010-10-20 6:25 ` [PATCH 2/2] arm: omap: zoom: substitute gpio number with symbolic name Felipe Balbi
2010-11-04 12:33 ` [PATCH 0/2] Combine zoom board-files Felipe Balbi
2010-11-05 21:43 ` Tony Lindgren [this message]
2010-11-06 0:52 ` Felipe Balbi
-- strict thread matches above, loose matches on Subject: below --
2010-11-08 6:56 [PATCH 0/2] combine " Felipe Balbi
2010-11-08 6:56 ` Felipe Balbi
2010-11-09 0:58 ` Tony Lindgren
2010-11-09 0:58 ` Tony Lindgren
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=20101105214358.GX9264@atomide.com \
--to=tony@atomide.com \
--cc=balbi@ti.com \
--cc=gadiyar@ti.com \
--cc=linux-omap@vger.kernel.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 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.