From: Tony Lindgren <tony@atomide.com>
To: Olof Johansson <olof@lixom.net>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 1/7] omap non-critical fixes for v3.7 merge window
Date: Mon, 17 Sep 2012 09:46:08 -0700 [thread overview]
Message-ID: <20120917164608.GK4521@atomide.com> (raw)
In-Reply-To: <20120917031725.GD13322@quad.lixom.net>
* Olof Johansson <olof@lixom.net> [120916 20:18]:
> On Thu, Sep 13, 2012 at 07:34:04PM -0700, Tony Lindgren wrote:
> > * Tony Lindgren <tony@atomide.com> [120913 19:20]:
> > > The following changes since commit 55d512e245bc7699a8800e23df1a24195dd08217:
> > >
> > > Linux 3.6-rc5 (2012-09-08 16:43:45 -0700)
> > >
> > > are available in the git repository at:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-fixes-noncritical-for-v3.7
> > >
> > > for you to fetch changes up to 3c5dc4a7daa6e64e39412fe9c7daa298834de623:
> > >
> > > ARM: OMAP4: wakeupgen: remove duplicate AUXCOREBOOT* read/write (2012-09-12 21:14:34 -0700)
> > >
> > > ----------------------------------------------------------------
> > > Non critical omap fixes that we not considered necessary
> > > for the v3.6 -rc cycle.
> > >
> > > ----------------------------------------------------------------
> >
> > Oops forgot to push out some of the tags and only this one
> > seems to got sent. Still a valid pull request, but I'll repost
> > the whole series of them.
>
> Ah, I noticed this now. And it also explains why I got 4 copies of all pull
> requests, they all looked identical until the one that was missing a tag,
> I suppose. :)
Yes sorry for the extra spam, looks like you already found the right
tag for the am33xx changes.
Thanks,
Tony
next prev parent reply other threads:[~2012-09-17 16:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <pull-1347589125-283636>
2012-09-14 2:18 ` [GIT PULL 2/7] omap device changes for v3.7 merge window Tony Lindgren
2012-09-14 2:18 ` [GIT PULL 4/7] omap custom atag removal " Tony Lindgren
2012-09-14 2:18 ` [GIT PULL 3/7] omap gpmc cleanup " Tony Lindgren
2012-09-14 2:18 ` [GIT PULL 5/7] omap sparse irq and local hardware.h " Tony Lindgren
2012-09-17 3:06 ` Olof Johansson
2012-09-14 2:18 ` [GIT PULL 7/7] am33xx hwmod data " Tony Lindgren
2012-09-17 3:16 ` Olof Johansson
2012-09-14 2:18 ` [GIT PULL 6/7] omap makefile and sparse cleanup " Tony Lindgren
2012-09-14 2:34 ` [GIT PULL 1/7] omap non-critical fixes " Tony Lindgren
2012-09-17 3:17 ` Olof Johansson
2012-09-17 16:46 ` Tony Lindgren [this message]
[not found] ` <5052940c.c8cae00a.65bd.ffffc8b2SMTPIN_ADDED@mx.google.com>
2012-09-17 2:51 ` [GIT PULL 2/7] omap device changes " Olof Johansson
[not found] ` <5052940d.06d3e00a.5f71.ffffd0d4SMTPIN_ADDED@mx.google.com>
2012-09-17 2:52 ` [GIT PULL 3/7] omap gpmc cleanup " Olof Johansson
[not found] ` <5052940f.d49de50a.7924.1155SMTPIN_ADDED@mx.google.com>
2012-09-17 2:52 ` [GIT PULL 4/7] omap custom atag removal " Olof Johansson
2012-09-14 2:18 [GIT PULL 1/7] omap non-critical fixes " Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2012-09-14 2:18 Tony Lindgren
2012-09-14 2:34 Tony Lindgren
2012-09-14 2:34 Tony Lindgren
[not found] <50529409.d487e50a.2f08.0ac6SMTPIN_ADDED@mx.google.com>
2012-09-17 2:51 ` 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=20120917164608.GK4521@atomide.com \
--to=tony@atomide.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=olof@lixom.net \
/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).