public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Sergey Lapin <slapinid@gmail.com>
Cc: "Premi, Sanjeev" <premi@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: OMAP3: enabling CPU idle leads to panic
Date: Wed, 25 Nov 2009 09:31:18 -0800	[thread overview]
Message-ID: <87iqcyh5p5.fsf@deeprootsystems.com> (raw)
In-Reply-To: <48239d390911250737q35fc602fu9bce0b0f96f6970d@mail.gmail.com> (Sergey Lapin's message of "Wed\, 25 Nov 2009 18\:37\:52 +0300")

Sergey Lapin <slapinid@gmail.com> writes:

> On Tue, Nov 24, 2009 at 11:21 PM, Premi, Sanjeev <premi@ti.com> wrote:
>> From: Kevin Hilman [khilman@deeprootsystems.com]
>> Sent: Tuesday, November 24, 2009 11:57 PM
>> To: Sergey Lapin; Premi, Sanjeev
>> Cc: linux-omap@vger.kernel.org
>> Subject: Re: OMAP3: enabling CPU idle leads to panic
>>
>> Sergey Lapin <slapinid@gmail.com> writes:
>>
>>> I use PM branch merged with linux-omap branch.
>>
>> Not sure what this means.  PM branch is already based at linux-omap
>> master branch.  You'll need to be more specific, ideally with commit
>> IDs.
>
> I do git branch tmp origin/master
> git checkout -f tmp
> git merge origin/pm

The pm branch is already based on l-o master, but perhaps not the very
latest.  Instead of the above can you just do

git branch tmp origin/pm
git checkout -f tmp

> git merge origin/mybranch

It might if you base your 'mybranch' at the same merge point that the
pm branch is based at.  You can find the merge point using:

git merge-base origin/master origin/pm

Kevin

  reply	other threads:[~2009-11-25 17:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-24 15:13 OMAP3: enabling CPU idle leads to panic Sergey Lapin
2009-11-24 18:27 ` Kevin Hilman
2009-11-24 20:21   ` Premi, Sanjeev
2009-11-25 15:37     ` Sergey Lapin
2009-11-25 17:31       ` Kevin Hilman [this message]
2009-11-27 10:02         ` Sergey Lapin
2009-11-27 10:48           ` Sergey Lapin
2009-11-27 11:02             ` Premi, Sanjeev
2009-11-27 11:32               ` Sergey Lapin
2009-11-27 11:36                 ` Sergey Lapin
2009-11-27 12:02                   ` Sergey Lapin
2009-11-27 12:18                     ` Premi, Sanjeev
2009-11-27 12:37                       ` Sergey Lapin
2009-11-27 12:43                         ` Premi, Sanjeev

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=87iqcyh5p5.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=premi@ti.com \
    --cc=slapinid@gmail.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