linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: OMAP: hwmod/PMU/PRCM patches for 3.7
Date: Sun, 23 Sep 2012 19:30:31 -0700	[thread overview]
Message-ID: <20120924023031.GW28835@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1209240102290.31370@utopia.booyaka.com>

* Paul Walmsley <paul@pwsan.com> [120923 18:09]:
> On Sun, 23 Sep 2012, Tony Lindgren wrote:
> 
> > Or maybe it's possible to split the series into smaller chunks
> > that can be pulled in to the existing branches without causing
> > new merge conflicts?
> 
> Well here's what I did, hopefully it's suitable.  Built a tag with all of 
> the clock and hwmod/runtime PM patches together, and based it on v3.6-rc6 
> + omap-cleanup-b-for-3.7 + cleanup-fixes-for-v3.7 + 
> omap-devel-am33xx-for-v3.7.  All of these are upstream.
> 
> Then I did a test merge with your commit 
> 219e2d6f43760509a0f0a084e8aa4711efb78c56:
> 
>   git checkout -b temp_tmlind_merge
>   git reset --hard 219e2d6f43760509a0f0a084e8aa4711efb78c56
>   git merge omap-devel-b-c-2-for-3.7
> 
> There are two conflicts, both trivial, and the patch below is how they got 
> resolved here.
> 
> Then probably you'll want to add Santosh's branch back in on top of that.

OK thanks, that should work. The nasty merge conflicts seem to have been
caused by mostly commit df3d17e0 (ARM: pmu: remove arm_pmu_type enumeration)
that easily causes a nasty mis-merge of omap_init_pmu() and omap_init_rng()
without removing omap_init_pmu() which your patches move to a different
location.

Regards,

Tony

  reply	other threads:[~2012-09-24  2:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21  1:04 [GIT PULL] ARM: OMAP: hwmod/PMU/PRCM patches for 3.7 Paul Walmsley
2012-09-21 20:53 ` Tony Lindgren
2012-09-21 23:10   ` Tony Lindgren
2012-09-22  0:03     ` Paul Walmsley
2012-09-22  0:21       ` Tony Lindgren
2012-09-22 17:47         ` Paul Walmsley
2012-09-23 19:09           ` Tony Lindgren
2012-09-23 21:06             ` Tony Lindgren
2012-09-24  1:08               ` Paul Walmsley
2012-09-24  2:30                 ` Tony Lindgren [this message]
2012-09-24 19:51                   ` Paul Walmsley
2012-09-23 22:59             ` Paul Walmsley
2012-09-22  5:40     ` Paul Walmsley
2012-09-22 15:44       ` Tony Lindgren

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=20120924023031.GW28835@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.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 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).