From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH 1/4] omap: igep0020: name refactoring for future merge with IGEP3
Date: Tue, 17 May 2011 10:53:46 +0300 [thread overview]
Message-ID: <20110517075345.GQ5323@atomide.com> (raw)
In-Reply-To: <BANLkTikJaN=Q2RgrA7Hz-ye2BCOjNK42zA@mail.gmail.com>
* Enric Balletb? i Serra <eballetbo@gmail.com> [110516 10:11]:
> Hi Mike,
>
> The only comment I wanted to do is maybe I prefer rename the
> board-igep0020 to board-igep00x0 to be more generic. Apart from this
> these patch series looks good for me and has my ack. Thanks.
I suggest we do the rename separately later on. Otherwise it
easily gets classified as "crazy churn" type of patch, so best
to stick to just code coalescing and fixes for this merge window.
Tony
next prev parent reply other threads:[~2011-05-17 7:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 21:40 [RESEND PATCH 0/4] omap: merge IGEP v2 and v3 Mike Rapoport
2011-05-12 21:40 ` [RESEND PATCH 1/4] omap: igep0020: name refactoring for future merge with IGEP3 Mike Rapoport
2011-05-16 7:15 ` Enric Balletbò i Serra
2011-05-17 7:53 ` Tony Lindgren [this message]
2011-05-17 7:57 ` Enric Balletbò i Serra
2011-05-17 10:33 ` Tony Lindgren
2011-05-18 9:05 ` Igor Grinberg
2011-05-12 21:40 ` [RESEND PATCH 2/4] omap: igep0020: minor refactoring Mike Rapoport
2011-05-13 18:44 ` Arnd Bergmann
2011-05-15 18:50 ` mike at compulab.co.il
2011-05-15 20:27 ` Arnd Bergmann
2011-05-16 7:17 ` Enric Balletbò i Serra
2011-05-12 21:40 ` [RESEND PATCH 3/4] omap: igep0020: add support for IGEP3 Mike Rapoport
2011-05-12 21:40 ` [RESEND PATCH 4/4] omap: drop board-igep0030.c Mike Rapoport
2011-05-16 7:18 ` Enric Balletbò i Serra
2011-05-13 7:27 ` [RESEND PATCH 0/4] omap: merge IGEP v2 and v3 Enric Balletbò i Serra
2011-05-13 8:42 ` mike at compulab.co.il
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=20110517075345.GQ5323@atomide.com \
--to=tony@atomide.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).