From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Linux OMAP Mailing List <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 0/4] RETU fetch IRQ via struct resource
Date: Mon, 14 Feb 2011 15:22:42 -0800 [thread overview]
Message-ID: <20110214232242.GS20795@atomide.com> (raw)
In-Reply-To: <20110214190001.GT2549@legolas.emea.dhcp.ti.com>
* Felipe Balbi <balbi@ti.com> [110214 10:58]:
> Hi,
>
> On Thu, Feb 10, 2011 at 12:21:17PM +0200, Felipe Balbi wrote:
> > here are 4 very quick patches to grab IRQ
> > via struct resource. Now all these changes
> > need to be ported to Tahvo. I'm not sure
> > I'll have any time to look at that for a
> > while, though.
OK, great those four are working. I've applied them
to the cbus branch.
> Want me to re-send all patches or you can pull from my cbus branch to
> test ?
Hmm well maybe send the new ones? Then I can pull assuming you
rebase on the cbus branch. That's usable now too and up to v2.6.38-rc4.
> Any taker for fixing tahvo ? All you have to do is port the changes done
> in retu to tahvo. Tahvo is a lot simpler than retu though.
It will be at least few weeks before I can do anything except
look and merge patches..
Tony
next prev parent reply other threads:[~2011-02-14 23:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 10:21 [PATCH 0/4] RETU fetch IRQ via struct resource Felipe Balbi
2011-02-10 10:21 ` [PATCH 1/4] cbus: retu: pass " Felipe Balbi
2011-02-10 10:21 ` [PATCH 2/4] cbus: retu: headset: grab " Felipe Balbi
2011-02-10 10:21 ` [PATCH 3/4] cbus: retu: pwrbutton: " Felipe Balbi
2011-02-10 10:21 ` [PATCH 4/4] cbus: retu: rtc: " Felipe Balbi
2011-02-14 19:00 ` [PATCH 0/4] RETU fetch " Felipe Balbi
2011-02-14 23:22 ` Tony Lindgren [this message]
2011-02-15 8:08 ` 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=20110214232242.GS20795@atomide.com \
--to=tony@atomide.com \
--cc=balbi@ti.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 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.