From: Tony Lindgren <tony@atomide.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Olof Johansson <olof@lixom.net>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 1/7] non-critical fixes part3 for upcoming merge window
Date: Wed, 14 Mar 2012 10:26:01 -0700 [thread overview]
Message-ID: <20120314172600.GP12083@atomide.com> (raw)
In-Reply-To: <201203141658.08234.arnd@arndb.de>
* Arnd Bergmann <arnd@arndb.de> [120314 10:00]:
> On Wednesday 14 March 2012, Tony Lindgren wrote:
> > * Olof Johansson <olof@lixom.net> [120310 10:26]:
> > > On Thu, Mar 08, 2012 at 12:53:29PM -0800, Tony Lindgren wrote:
> > > > Hi Olof,
> > > >
> > > > Here are two more pre-emptive fixes for upcoming merge
> > > > window to pull into arm-soc/next/fixes-non-critical.
> > > >
> > > > Now with the fixes finallny out of the way after all
> > > > the cleanup related changes, as a reply to this pull
> > > > request I'm posting some more pull requests for cleanup
> > > > and some minor board changes.
> > >
> > > Pulled request 1-7.
> >
> > Now with another -rc, can you please pull in also
> > 2 - 7 in this series?
>
> Hi Tony,
>
> I'm pretty sure that Olof pulled all the branches the first time
> around, i.e. 1-7, not just 1/7. Please check the for-next
> branch and tell us if there is anything still missing.
Indeed, all seven are there! Thanks,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/7] non-critical fixes part3 for upcoming merge window
Date: Wed, 14 Mar 2012 10:26:01 -0700 [thread overview]
Message-ID: <20120314172600.GP12083@atomide.com> (raw)
In-Reply-To: <201203141658.08234.arnd@arndb.de>
* Arnd Bergmann <arnd@arndb.de> [120314 10:00]:
> On Wednesday 14 March 2012, Tony Lindgren wrote:
> > * Olof Johansson <olof@lixom.net> [120310 10:26]:
> > > On Thu, Mar 08, 2012 at 12:53:29PM -0800, Tony Lindgren wrote:
> > > > Hi Olof,
> > > >
> > > > Here are two more pre-emptive fixes for upcoming merge
> > > > window to pull into arm-soc/next/fixes-non-critical.
> > > >
> > > > Now with the fixes finallny out of the way after all
> > > > the cleanup related changes, as a reply to this pull
> > > > request I'm posting some more pull requests for cleanup
> > > > and some minor board changes.
> > >
> > > Pulled request 1-7.
> >
> > Now with another -rc, can you please pull in also
> > 2 - 7 in this series?
>
> Hi Tony,
>
> I'm pretty sure that Olof pulled all the branches the first time
> around, i.e. 1-7, not just 1/7. Please check the for-next
> branch and tell us if there is anything still missing.
Indeed, all seven are there! Thanks,
Tony
next prev parent reply other threads:[~2012-03-14 17:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4f591c4d.e471340a.1f3f.3a69SMTPIN_ADDED@mx.google.com>
2012-03-10 18:24 ` [GIT PULL 1/7] non-critical fixes part3 for upcoming merge window Olof Johansson
2012-03-10 18:24 ` Olof Johansson
2012-03-14 16:35 ` Tony Lindgren
2012-03-14 16:35 ` Tony Lindgren
2012-03-14 16:58 ` Arnd Bergmann
2012-03-14 16:58 ` Arnd Bergmann
2012-03-14 17:26 ` Tony Lindgren [this message]
2012-03-14 17:26 ` Tony Lindgren
2012-03-08 20:53 Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2012-03-08 20:53 Tony Lindgren
2012-03-08 20:53 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=20120314172600.GP12083@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 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.