From: Ameya Palande <ameya.palande@nokia.com>
To: Tony Lindgren <tony@atomide.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Doyu Hiroshi (Nokia-D/Helsinki)" <hiroshi.doyu@nokia.com>,
Nishanth Menon <nm@ti.com>
Subject: Re: tidspbridge git repository
Date: Fri, 27 Mar 2009 15:06:22 +0200 [thread overview]
Message-ID: <49CCCF4E.2010708@nokia.com> (raw)
In-Reply-To: <20090323194711.GI29546@atomide.com>
Hi Tony,
ext Tony Lindgren wrote:
> * ameya.palande@nokia.com <ameya.palande@nokia.com> [090323 00:42]:
>> Hi Tony,
>>
>> I have collected latest patches for tidspbridge at:
>> git://gitorious.org/tidspbridge/mainline.git
>>
>> Branch is: tidspbridge
>>
>> It is based on your pm branch.
>> Can you pull it to your tidspbridge branch?
>
> What dependencies are there to the PM branch?
>
> To me it sounds like you should rebase your tidspbridge branch
> against the mainline kernel as the drivers should be arch
> independent.
>
> If something is missing from the mainline kernel to rebase and
> compile tidspbridge against the mainline, we need to fix those
> issues.
>
> Regards,
>
> Tony
I have rebased tidspbridge patches on top of current pm branch.
Currently bridge depends on some pm features which are not yet in
mainline.
But at least now it can be compiled for your latest pm branch which
I guess is in turn based on 2.6.29
Here is the git URL:
git://gitorious.org/tidspbridge/mainline.git
Branch is: tidspbridge-2.6.29-pm
Thanks!
Cheers,
Ameya.
next prev parent reply other threads:[~2009-03-27 13:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 7:41 tidspbridge git repository ameya.palande
2009-03-23 7:44 ` Menon, Nishanth
2009-03-23 7:58 ` Ameya Palande
2009-03-23 8:55 ` Menon, Nishanth
2009-03-23 11:22 ` Ameya Palande
2009-03-23 12:15 ` Menon, Nishanth
2009-03-23 19:47 ` Tony Lindgren
2009-03-24 23:27 ` Felipe Contreras
2009-03-27 13:06 ` Ameya Palande [this message]
2009-03-27 16:50 ` Tony Lindgren
2009-04-27 2:30 ` Gregoire Gentil
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=49CCCF4E.2010708@nokia.com \
--to=ameya.palande@nokia.com \
--cc=hiroshi.doyu@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--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