public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-omap@vger.kernel.org
Subject: Re: [ANNOUNCE:RFC] convert OMAP to use clkdev
Date: Sat, 24 Jan 2009 11:01:36 -0800	[thread overview]
Message-ID: <20090124190130.GC7172@atomide.com> (raw)
In-Reply-To: <20090124184053.GC27329@n2100.arm.linux.org.uk>

* Russell King - ARM Linux <linux@arm.linux.org.uk> [090124 10:42]:
> On Sat, Jan 24, 2009 at 10:32:29AM -0800, Tony Lindgren wrote:
> > * Russell King - ARM Linux <linux@arm.linux.org.uk> [090124 09:38]:
> > > I had given up all hope of ever seeing the omap-clks1 branch in mainline.
> > > Really.  Until I saw a comment from you about apparantly wanting to see it
> > > upstream.  However, I still have a very big question whether any of this
> > > work will ever reach mainline, especially since my experimental omap-clks1
> > > branch seems to have been broken up with random bits applied to your tree
> > > with zero discussion with me.
> > 
> > Paul has spent some time to merge some of your earlier omap-clks1
> > stuff into linux-omap tree. Manually merging them, there's really no
> > other way to merge these changes. And Paul posted some of your earlier
> > omap-clks1 patches to this list along with some other patches before
> > they got merged.
> > 
> > Anyways, too late to bitch. Merging this stuff is going to be a pain.
> > And in the long run we need both Russell's and Paul's patches. So let's
> > just figure out a way how we can get it all merged and into the mainline
> > tree.
> 
> If Paul sends me his changes, I'm entirely willing to do the dovetailing
> work to get them merged with my changes.  I already do that - what you
> see as the changes between clks1 and clks2 were resorted this morning
> before sending that email out.  There's interdependencies between each
> commit which make such operations non-trivial with traditional git usage.
> I have my own scripts which make it possible to move, delete, and merge
> a set of commits and patches together.
> 
> Therefore, it probably makes sense for me to do it.

Wow, that's the best thing I've ever seen during all the merge hells!

I'll keep the clks-testing branch updated so we all can test it easily,
and then we'll just flip linux-omap to use that branch for the clocks
once everything is merged.

Let me know if I can help with anything else!

Tony

  reply	other threads:[~2009-01-24 19:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-24 12:03 [ANNOUNCE:RFC] convert OMAP to use clkdev Russell King - ARM Linux
2009-01-24 16:41 ` Woodruff, Richard
2009-01-24 16:55   ` Russell King - ARM Linux
2009-01-24 17:04 ` Tony Lindgren
2009-01-24 17:38   ` Russell King - ARM Linux
2009-01-24 18:32     ` Tony Lindgren
2009-01-24 18:40       ` Russell King - ARM Linux
2009-01-24 19:01         ` Tony Lindgren [this message]
2009-01-28 10:17           ` Russell King - ARM Linux
2009-01-28 15:59             ` Tony Lindgren
2009-01-28 16:10               ` Russell King - ARM Linux
2009-01-28 17:15                 ` Tony Lindgren
2009-01-24 19:03         ` Paul Walmsley
2009-01-27  1:00 ` Paul Walmsley

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=20090124190130.GC7172@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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