From: Kevin Hilman <khilman@ti.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] omap cleanup part1 for v3.2 merge window
Date: Thu, 22 Sep 2011 09:15:05 -0700 [thread overview]
Message-ID: <87hb44v9iu.fsf@ti.com> (raw)
In-Reply-To: <201109221633.14887.arnd@arndb.de> (Arnd Bergmann's message of "Thu, 22 Sep 2011 16:33:14 +0200")
Arnd Bergmann <arnd@arndb.de> writes:
> On Wednesday 21 September 2011, Kevin Hilman wrote:
>> Found. Patch below.
>>
>> If this one is OK, I'll push to my for_3.2/voltage-cleanup branch (which
>> is already pulled into arm-soc/next/voltage) so just re-pulling will
>> pick up the fix.
>
> Looks good to me, it's always nice when a bug fix is also a cleanup ;-)
>
OK, added it to the branch you've already pulled[1], if you (re)pull,
you'll get the fix too.
Thanks,
Kevin
[1] git://gitorious.org/khilman/linux-omap-pm.git for_3.2/voltage_cleanup
WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap cleanup part1 for v3.2 merge window
Date: Thu, 22 Sep 2011 09:15:05 -0700 [thread overview]
Message-ID: <87hb44v9iu.fsf@ti.com> (raw)
In-Reply-To: <201109221633.14887.arnd@arndb.de> (Arnd Bergmann's message of "Thu, 22 Sep 2011 16:33:14 +0200")
Arnd Bergmann <arnd@arndb.de> writes:
> On Wednesday 21 September 2011, Kevin Hilman wrote:
>> Found. Patch below.
>>
>> If this one is OK, I'll push to my for_3.2/voltage-cleanup branch (which
>> is already pulled into arm-soc/next/voltage) so just re-pulling will
>> pick up the fix.
>
> Looks good to me, it's always nice when a bug fix is also a cleanup ;-)
>
OK, added it to the branch you've already pulled[1], if you (re)pull,
you'll get the fix too.
Thanks,
Kevin
[1] git://gitorious.org/khilman/linux-omap-pm.git for_3.2/voltage_cleanup
next prev parent reply other threads:[~2011-09-22 16:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-17 1:46 [GIT PULL] omap cleanup part1 for v3.2 merge window Tony Lindgren
2011-09-17 1:46 ` Tony Lindgren
2011-09-20 20:01 ` Arnd Bergmann
2011-09-20 20:01 ` Arnd Bergmann
2011-09-20 20:55 ` Tony Lindgren
2011-09-20 20:55 ` Tony Lindgren
2011-09-20 21:34 ` Arnd Bergmann
2011-09-20 21:34 ` Arnd Bergmann
2011-09-20 21:46 ` Arnd Bergmann
2011-09-20 21:46 ` Arnd Bergmann
2011-09-20 22:33 ` Tony Lindgren
2011-09-20 22:33 ` Tony Lindgren
2011-09-21 7:06 ` Arnd Bergmann
2011-09-21 7:06 ` Arnd Bergmann
2011-09-22 0:52 ` Tony Lindgren
2011-09-22 0:52 ` Tony Lindgren
2011-09-21 9:28 ` Arnd Bergmann
2011-09-21 9:28 ` Arnd Bergmann
2011-09-21 13:51 ` Tony Lindgren
2011-09-21 13:51 ` Tony Lindgren
2011-09-21 16:43 ` Kevin Hilman
2011-09-21 16:43 ` Kevin Hilman
2011-09-22 14:33 ` Arnd Bergmann
2011-09-22 14:33 ` Arnd Bergmann
2011-09-22 16:15 ` Kevin Hilman [this message]
2011-09-22 16:15 ` Kevin Hilman
2011-09-23 22:53 ` Tony Lindgren
2011-09-23 22:53 ` Tony Lindgren
2011-09-30 20:04 ` Arnd Bergmann
2011-09-30 20:04 ` Arnd Bergmann
2011-09-20 23:25 ` [PATCH] ARM: OMAP2+: Fix missing inline functions for Makefile cleanup (Re: [GIT PULL] omap cleanup part1 for v3.2 merge window) Tony Lindgren
2011-09-20 23:25 ` 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=87hb44v9iu.fsf@ti.com \
--to=khilman@ti.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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.