From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] i.MX cleanup patches for next
Date: Mon, 16 Apr 2012 10:00:53 +0200 [thread overview]
Message-ID: <20120416080053.GQ3852@pengutronix.de> (raw)
In-Reply-To: <CAOesGMhk9tGokNwy1kdFDB+G08OYEEq9Uf1Qu=K=T8ufick2ag@mail.gmail.com>
On Sun, Apr 15, 2012 at 11:23:02AM -0700, Olof Johansson wrote:
> Hi,
>
>
> On Wed, Apr 11, 2012 at 1:44 AM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> > Hi Arnd, Olof,
> >
> > Please pull the following i.MX cleanup patches for next.
> >
> > Sascha
> >
> > The following changes since commit dd775ae2549217d3ae09363e3edb305d0fa19928:
> >
> > ?Linux 3.4-rc1 (2012-03-31 16:24:09 -0700)
> >
> > are available in the git repository at:
> >
> > ?git://git.pengutronix.de/git/imx/linux-2.6.git tags/imx-cleanup-20120411
> >
> > for you to fetch changes up to b0843e814737756a38003afe663a626653b66f58:
> >
> > ?efikamx: match machine descriptions with legacy (2012-04-02 11:20:38 +0200)
> >
> > ----------------------------------------------------------------
> > i.MX misc cleanups
> >
> > ----------------------------------------------------------------
> > Hector Oron (1):
> > ? ? ?efikamx: match machine descriptions with legacy
> >
> > Uwe Kleine-K?nig (1):
> > ? ? ?ARM: imx/mx21ads: remove unneeded cast
>
> Same comment as on the other pull request regarding prefix on the efikamx patch.
>
> Also, no need to date the tags -- the tag itself contains the date
> (Linus has been complaining to people who add redundant data to the
> tag contents when they send tags to him).
Ok, won't do this in future. I just thought it might be a good idea,
because otherwise I end up with the same tag names in the next pull
request.
>
> Branch contents otherwise looks OK, so respin and send a fresh pull
> request and we'll merge it in.
Here it is:
The following changes since commit dd775ae2549217d3ae09363e3edb305d0fa19928:
Linux 3.4-rc1 (2012-03-31 16:24:09 -0700)
are available in the git repository at:
git://git.pengutronix.de/git/imx/linux-2.6.git tags/arm-imx-cleanup
for you to fetch changes up to 33076883bc45bfdd5fa5c9bff7f012a460719aba:
ARM: i.MX: efikamx: match machine descriptions with legacy (2012-04-16 09:54:50 +0200)
----------------------------------------------------------------
ARM: i.MX: misc board cleanups
----------------------------------------------------------------
Hector Oron (1):
ARM: i.MX: efikamx: match machine descriptions with legacy
Uwe Kleine-K?nig (1):
ARM: imx/mx21ads: remove unneeded cast
arch/arm/mach-imx/mach-mx21ads.c | 3 +--
arch/arm/mach-imx/mach-mx51_efikamx.c | 3 +--
arch/arm/mach-imx/mach-mx51_efikasb.c | 2 +-
3 files changed, 3 insertions(+), 5 deletions(-)
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2012-04-16 8:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 8:44 [GIT PULL] i.MX cleanup patches for next Sascha Hauer
2012-04-15 18:23 ` Olof Johansson
2012-04-16 8:00 ` Sascha Hauer [this message]
2012-04-25 6:25 ` Sascha Hauer
2012-04-25 18:07 ` Olof Johansson
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=20120416080053.GQ3852@pengutronix.de \
--to=s.hauer@pengutronix.de \
--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).