From: Tony Lindgren <tony@atomide.com>
To: Olof Johansson <olof@lixom.net>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: [GIT PULL] Borderline fixes for v3.2-rc6
Date: Thu, 22 Dec 2011 09:21:43 -0800 [thread overview]
Message-ID: <20111222172143.GI24444@atomide.com> (raw)
In-Reply-To: <CAOesGMihx_1Ay6qEfynXw8Xqmu9xzgLeEj0UjkfY8g7e9jUaDw@mail.gmail.com>
* Olof Johansson <olof@lixom.net> [111222 08:42]:
> On Thu, Dec 22, 2011 at 9:11 AM, Tony Lindgren <tony@atomide.com> wrote:
> > Hi Olof,
> >
> > * Olof Johansson <olof@lixom.net> [111220 09:29]:
> >> On Tue, Dec 20, 2011 at 9:10 AM, Tony Lindgren <tony@atomide.com> wrote:
> >> >
> >> > I've branched it out into fixes-hwmod-regression with just that
> >> > same commit in it. The second patch in this series will be pulled in
> >> > with fixes-non-critical-part2. Updated pull request below.
> >>
> >> Thanks, I pulled fixes-hwmod-regression into fixes and fixes-hwmod
> >> into next/fixes-non-critical.
> >
> > Just checking.. Looks like you pulled fixes-hwmod into a new branch
> > named fixes-non-critical-part2, but did not pull the same name branch
> > fixes-non-critical-part2 that I posted?
> >
> > That's this pull request:
> >
> > http://www.spinics.net/lists/linux-omap/msg62050.html
>
> Grmbl, thanks for catching that. I'll sort it out at this end.
OK 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] Borderline fixes for v3.2-rc6
Date: Thu, 22 Dec 2011 09:21:43 -0800 [thread overview]
Message-ID: <20111222172143.GI24444@atomide.com> (raw)
In-Reply-To: <CAOesGMihx_1Ay6qEfynXw8Xqmu9xzgLeEj0UjkfY8g7e9jUaDw@mail.gmail.com>
* Olof Johansson <olof@lixom.net> [111222 08:42]:
> On Thu, Dec 22, 2011 at 9:11 AM, Tony Lindgren <tony@atomide.com> wrote:
> > Hi Olof,
> >
> > * Olof Johansson <olof@lixom.net> [111220 09:29]:
> >> On Tue, Dec 20, 2011 at 9:10 AM, Tony Lindgren <tony@atomide.com> wrote:
> >> >
> >> > I've branched it out into fixes-hwmod-regression with just that
> >> > same commit in it. The second patch in this series will be pulled in
> >> > with fixes-non-critical-part2. Updated pull request below.
> >>
> >> Thanks, I pulled fixes-hwmod-regression into fixes and fixes-hwmod
> >> into next/fixes-non-critical.
> >
> > Just checking.. Looks like you pulled fixes-hwmod into a new branch
> > named fixes-non-critical-part2, but did not pull the same name branch
> > fixes-non-critical-part2 that I posted?
> >
> > That's this pull request:
> >
> > http://www.spinics.net/lists/linux-omap/msg62050.html
>
> Grmbl, thanks for catching that. I'll sort it out at this end.
OK thanks!
Tony
next prev parent reply other threads:[~2011-12-22 17:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 19:42 [GIT PULL] Borderline fixes for v3.2-rc6 Tony Lindgren
2011-12-19 19:42 ` Tony Lindgren
2011-12-20 4:52 ` Olof Johansson
2011-12-20 4:52 ` Olof Johansson
2011-12-20 17:10 ` Tony Lindgren
2011-12-20 17:10 ` Tony Lindgren
2011-12-20 18:01 ` Olof Johansson
2011-12-20 18:01 ` Olof Johansson
2011-12-22 17:11 ` Tony Lindgren
2011-12-22 17:11 ` Tony Lindgren
2011-12-22 17:14 ` Olof Johansson
2011-12-22 17:14 ` Olof Johansson
2011-12-22 17:21 ` Tony Lindgren [this message]
2011-12-22 17:21 ` 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=20111222172143.GI24444@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.