mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Tony Lindgren <tony@atomide.com>
Cc: Paul Walmsley <paul@pwsan.com>,
	linux-arm-kernel@lists.arm.linux.org.uk,
	linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: OMAP clock fast-forward: an introduction to six series
Date: Thu, 29 Jan 2009 16:35:01 +0000	[thread overview]
Message-ID: <20090129163501.GE18233@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20090129162556.GA32148@atomide.com>

On Thu, Jan 29, 2009 at 08:25:58AM -0800, Tony Lindgren wrote:
> To me it does not matter which way the stuff gets merged. We just need
> to get it all merged.
> 
> If you guys can't get it merged and sorted out then it will all fall
> down on me. And then I have to use tools no smaller than a sledgehammer
> to merge it all, so the outcome won't be pretty!

Well, I've continued with my approach.  28 patches are currently merged
onto a follow-on branch (scattered throughout the series but in order)
and the result builds for my OMAP1, OMAP2 and OMAP3 test builds.

Patches which I've provided non-trivial comments on by and large haven't
been merged.  Once I've worked through the set, I'll provide a final list
of those outstanding so nothing should be lost.

I would appreciate someone _bouncing_ (not forwarding) the patches I'm
missing to linux@arm.linux.org.uk please.  Those being D6, E2 and F2.


  reply	other threads:[~2009-01-29 16:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-28 20:22 Paul Walmsley
2009-01-28 21:18 ` Russell King - ARM Linux
2009-01-29  7:05   ` Paul Walmsley
2009-01-29  8:11     ` Russell King - ARM Linux
2009-01-29  8:30       ` Russell King - ARM Linux
2009-01-29 16:25         ` Tony Lindgren
2009-01-29 16:35           ` Russell King - ARM Linux [this message]
2009-01-29 16:41             ` Tony Lindgren
2009-01-29 16:53               ` Tony Lindgren
2009-01-29 17:14                 ` Russell King - ARM Linux

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=20090129163501.GE18233@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.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

all inboxes | Powered by JetHome®