linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <felipe.balbi@nokia.com>
To: ext Tony Lindgren <tony@atomide.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [APPLIED] [PATCH omap-fixes v2] OMAP2/3: GPIO: do not attempt to wake-enable
Date: Thu, 19 Mar 2009 18:48:46 +0200	[thread overview]
Message-ID: <20090319164846.GA30655@scadufax.research.nokia.com> (raw)
In-Reply-To: <20090319165334.GK29546@atomide.com>

On Thu, Mar 19, 2009 at 05:53:35PM +0100, Tony Lindgren wrote:
> * Kevin Hilman <khilman@deeprootsystems.com> [090319 09:44]:
> > Tony Lindgren <tony@atomide.com> writes:
> > 
> > > This patch has been applied to the linux-omap
> > > by youw fwiendly patch wobot.
> > >
> > > Commit: 2ac496a208895c925aec1774a873b5b096b2d3f0
> > >
> > > PatchWorks
> > > http://patchwork.kernel.org/patch/10719/
> > >
> > > Git
> > > http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=commit;h=2ac496a208895c925aec1774a873b5b096b2d3f0
> > 
> > Tony, 
> > 
> > $SUBJECT on this commit seems to have been a bit mangled leaving
> > a not very clear commit log/history.
> 
> Heh looks like bad html parsing :) I'll revert and re-apply.

why do you even try to parse the html ?? patchworks hold it in mbox
format:

http://patchwork.kernel.org/patch/10719/mbox/

-- 
balbi

  reply	other threads:[~2009-03-19 17:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-09 22:14 [PATCH omap-fixes v2] OMAP2/3: GPIO: do not attempt to wake-enable GPIO bank IRQ Kevin Hilman
2009-03-18 22:07 ` [APPLIED] [PATCH omap-fixes v2] OMAP2/3: GPIO: do not attempt to wake-enable Tony Lindgren
2009-03-19 16:43   ` Kevin Hilman
2009-03-19 16:53     ` Tony Lindgren
2009-03-19 16:48       ` Felipe Balbi [this message]
2009-03-19 17:16       ` Tony Lindgren
2009-03-19 17:27         ` Felipe Balbi

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=20090319164846.GA30655@scadufax.research.nokia.com \
    --to=felipe.balbi@nokia.com \
    --cc=khilman@deeprootsystems.com \
    --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 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).