From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: Abraham Arce <abraham.arce.moreno@gmail.com>,
"Arce, Abraham" <x0066660@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Compilation: omap-for-linus omap2plus error
Date: Thu, 30 Sep 2010 07:18:38 -0700 [thread overview]
Message-ID: <87zkuziabl.fsf@deeprootsystems.com> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB030CD02FA5@dbde02.ent.ti.com> (Santosh Shilimkar's message of "Thu, 30 Sep 2010 13:25:17 +0530")
"Shilimkar, Santosh" <santosh.shilimkar@ti.com> writes:
>> > Is there any patch missing in omap-for-linus branch?
Short version:
Yes, there are several and the dependencies are taken care of in the
master branch.
Long version:
There are several changes that are going upstream for 2.6.37 that are
going through other trees (driver core, runtime PM core, i2c core, etc.)
In my tree, I keep these in my pm-backports branch, and for Tony's tree,
he has cherry-picked them into the omap-testing branch so they are
included in l-o master until the merge window opens.
So, even if you cherry pick the one patch, you may not have compile time
problems but you will have other runtime problems due to other
dependencies. So I strongly recommend just using l-o master.
Kevin
next prev parent reply other threads:[~2010-09-30 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 3:54 Compilation: omap-for-linus omap2plus error Abraham Arce
2010-09-30 4:16 ` Abraham Arce
2010-09-30 7:55 ` Shilimkar, Santosh
2010-09-30 8:55 ` Abraham Arce
2010-09-30 14:18 ` Kevin Hilman [this message]
2010-09-30 14:10 ` Ming Lei
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=87zkuziabl.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=abraham.arce.moreno@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.com \
--cc=x0066660@ti.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.