public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Russell King <linux@arm.linux.org.uk>,
	Johannes Berg <johannes@sipsolutions.net>,
	linux-omap-open-source@linux.omap.com,
	linux-pm <linux-pm@lists.linux-foundation.org>
Subject: Re: [linux-pm] [PATCH] power management: remove some useless code from arm platforms
Date: Wed, 2 May 2007 03:48:33 +0000	[thread overview]
Message-ID: <20070502034833.GC27201@atomide.com> (raw)
In-Reply-To: <20070428034137.GA7200@atomide.com>

* Tony Lindgren <tony@atomide.com> [070428 03:41]:
> Hi,
> 
> * Andrew Morton <akpm@linux-foundation.org> [070428 00:53]:
> > On Fri, 27 Apr 2007 01:12:26 +0400
> > Dmitry Krivoschekov <dmitry.krivoschekov@gmail.com> wrote:
> > 
> > > Johannes Berg wrote:
> > > > This patch kills some useless code omap1/omap2.
> > > Although the change looks harmless it'd be nice  CC-ing
> > > appropriate "arch" or "mach" lists.
> > > 
> > > Added omap list to CC.
> > > 
> > > BTW, you change OMAP stuff only, so your subject is slightly irrelevant.
> > > 
> > 
> > I'm not very comfortable handling OMAP code (Tony), ARM code (Russell) or
> > power-management code (Greg), and this patch is all three.
> 
> Well this patch will probably cause some minor merge conflicts with the
> pending omap patches, not a big deal though.

Looks like the omap pile still applies fine after Johannes' patches,
so no merge issue there :)

> > So ho hum.  I queued it up with Greg as the arbitrary target, but I'm not
> > sure that is really appopriate.  Probably it should have been Tony, but
> > Tony's tree is hiding from me.
> 
> The omap tree is available at [1] and the currently pending patches
> pile at [2].
> 
> > I guess we should look at dragging the OMAP git tree into -mm.
> 
> I thought Russell is about to apply the pending omap patches to his
> tree, so let's wait until we hear from him.
> 
> Assuming Russell applies the pending omap patches, things should
> be pretty much in sync with the mainline tree and linux-omap tree for
> the core omap support.
> 
> There will be some driver and PM patches that would fit to -mm tree
> though. At least the voltage framework, and possibly the DSP code later
> on, come to mind.
> 
> Regards,
> 
> Tony
> 
> [1] git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git
> [2] git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git omap-upstream-after-clocksource

      reply	other threads:[~2007-05-02  3:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1177604177.6814.81.camel@johannes.berg>
2007-04-26 21:12 ` [PATCH] power management: remove some useless code from arm platforms Dmitry Krivoschekov
2007-04-27  9:38   ` Johannes Berg
2007-04-28  0:53   ` Andrew Morton
2007-04-28  3:41     ` Tony Lindgren
2007-05-02  3:48       ` Tony Lindgren [this message]

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=20070502034833.GC27201@atomide.com \
    --to=tony@atomide.com \
    --cc=akpm@linux-foundation.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=linux-pm@lists.linux-foundation.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