From: Kevin Hilman <khilman@deeprootsystems.com>
To: Tero.Kristo@nokia.com
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/2] OMAP3: GPIO off-mode fixes
Date: Wed, 11 Mar 2009 15:11:52 -0700 [thread overview]
Message-ID: <87wsavogk7.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1F18D6510CF0474A8C9500565A7E41A20378951294@NOK-EUMSG-02.mgdnok.nokia.com> (Tero Kristo's message of "Wed\, 11 Mar 2009 11\:04\:34 +0100")
<Tero.Kristo@nokia.com> writes:
> The first patch in this set contains a small bug, missing kfree() for one of the dynamically reserved arrays during init in error path. Sending a fixed patch now.
>
Thanks Tero. I will undo the first version and re-push with this version.
Kevin
>
>>-----Original Message-----
>>From: ext Kevin Hilman [mailto:khilman@deeprootsystems.com]
>>Sent: 09 March, 2009 20:48
>>To: Kristo Tero (Nokia-D/Tampere)
>>Cc: linux-omap@vger.kernel.org
>>Subject: Re: [PATCH 0/2] OMAP3: GPIO off-mode fixes
>>
>>Tero Kristo <tero.kristo@nokia.com> writes:
>>
>>> These two patches add fixes to GPIO off-mode handling. First
>>patch is
>>> more important as it fixes a HW bug, second one just optimizes
>>> off-mode code a bit by removing a couple of unnecessary
>>registers from the context save.
>>
>>Thanks, pushing both patches to PM branch.
>>
>>Kevin
>>
prev parent reply other threads:[~2009-03-11 22:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 11:46 [PATCH 0/2] OMAP3: GPIO off-mode fixes Tero Kristo
2009-03-06 11:46 ` [PATCH 1/2] OMAP3: PM: Fixed glitches in GPIO outputs during off-mode transitions Tero Kristo
2009-03-06 11:46 ` [PATCH 2/2] OMAP3: GPIO: Removed a couple of unneeded registers from context save/restore Tero Kristo
2009-03-09 18:48 ` [PATCH 0/2] OMAP3: GPIO off-mode fixes Kevin Hilman
2009-03-11 10:04 ` Tero.Kristo
2009-03-11 22:11 ` Kevin Hilman [this message]
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=87wsavogk7.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=Tero.Kristo@nokia.com \
--cc=linux-omap@vger.kernel.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