linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Viresh Kumar <viresh.kumar@st.com>,
	Srinidhi Kasagar <srinidhi.kasagar@stericsson.com>,
	Kevin Hilman <khilman@deeprootsystems.com>,
	Anton Vorontsov <avorontsov@mvista.com>,
	Lennert Buytenhek <kernel@wantstofly.org>,
	Kukjin Kim <kgene.kim@samsung.com>,
	Erik Gilling <konkers@android.com>,
	linux-sh@vger.kernel.org, Vincent Sanders <support@simtec.co.uk>,
	"Hans J. Koch" <hjk@linutronix.de>,
	Magnus Damm <magnus.damm@gmail.com>, Marc Singer <elf@buici.com>,
	Tony Lindgren <tony@atomide.com>,
	David Brown <davidb@codeaurora.org>,
	Alessandro Rubini <rubini@unipv.it>,
	Jiandong Zheng <jdzheng@broadcom.com>,
	Wan ZongShun <mcuos.com@gmail.com>,
	linux-arm-msm@vger.kernel.org, Olof Johansson <olof@lixom.net>,
	Ryan Mallon <ryan@bluewatersys.com>,
	linux-samsung-soc@vger.kernel.org,
	Ben Dooks <ben-linux@fluff.org>,
	linux-tegra@vger.kernel.org, linux-omap@vger.kernel.org,
	linux-arm-kernel
Subject: Re: [RFC 1/5] ARM: P2V: separate PHYS_OFFSET from platform definitions
Date: Wed, 5 Jan 2011 22:30:53 +0000	[thread overview]
Message-ID: <20110105223053.GN8638@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.00.1101041607110.22191@xanadu.home>

On Tue, Jan 04, 2011 at 04:10:44PM -0500, Nicolas Pitre wrote:
> On Tue, 4 Jan 2011, Russell King - ARM Linux wrote:
> 
> > This uncouple PHYS_OFFSET from the platform definitions, thereby
> > facilitating run-time computation of the physical memory offset.
> > 
> > Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
> 
> Acked-by: Nicolas Pitre <nicolas.pitre@linaro.org>
> 
> This might even be a good time to merge such patch now even if the later 
> patches don't make it into the next merge window as this would produce 
> fewer conflicts later.

I think waiting might be in order - MXC conflicts with this patch set
and needs rechecking to make sure it's right.  ATM, it's had no
visibility in linux-next.

However, it makes sense to get the likely to conflict bits in sooner
rather than later - or I need to publish them from my git tree in a
stable form so that people can include those changes in their patchsets.

  reply	other threads:[~2011-01-05 22:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-04 20:20 [RFC 0/5] runtime P2V translations Russell King - ARM Linux
2011-01-04 20:22 ` [RFC 1/5] ARM: P2V: separate PHYS_OFFSET from platform definitions Russell King - ARM Linux
2011-01-04 21:10   ` Nicolas Pitre
2011-01-05 22:30     ` Russell King - ARM Linux [this message]
2011-01-04 21:23   ` Uwe Kleine-König
2011-01-05  0:04     ` Russell King - ARM Linux
2011-01-05  6:25       ` Uwe Kleine-König
2011-01-05  3:28   ` viresh kumar
2011-01-05 17:04   ` H Hartley Sweeten
2011-01-06  5:02   ` Magnus Damm
2011-02-07 15:57     ` Tony Lindgren
2011-02-07 16:36   ` Jean-Christophe PLAGNIOL-VILLARD
2011-02-08 11:22   ` Wan ZongShun
2011-02-17  5:33   ` Kukjin Kim
2011-02-17 15:16   ` Eric Miao
2011-02-17 18:07     ` JD (Jiandong) Zheng
2011-01-04 20:22 ` [RFC 2/5] ARM: P2V: avoid initializers and assembly using PHYS_OFFSET Russell King - ARM Linux
2011-01-04 21:12   ` Nicolas Pitre
2011-01-06  8:51   ` Sascha Hauer
2011-01-06  9:08     ` Russell King - ARM Linux
2011-02-07 15:59       ` Tony Lindgren
2011-02-07 16:51   ` Uwe Kleine-König
2011-02-07 16:52     ` Uwe Kleine-König
2011-02-17  5:36   ` Kukjin Kim
2011-02-17 14:11   ` Russell King - ARM Linux
2011-02-17 16:19     ` David Brown
2011-02-17 15:16   ` Eric Miao
2011-02-17 14:15 ` [RFC 0/5] runtime P2V translations 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=20110105223053.GN8638@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=avorontsov@mvista.com \
    --cc=ben-linux@fluff.org \
    --cc=davidb@codeaurora.org \
    --cc=elf@buici.com \
    --cc=hjk@linutronix.de \
    --cc=jdzheng@broadcom.com \
    --cc=kernel@wantstofly.org \
    --cc=kgene.kim@samsung.com \
    --cc=khilman@deeprootsystems.com \
    --cc=konkers@android.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mcuos.com@gmail.com \
    --cc=nico@fluxnic.net \
    --cc=olof@lixom.net \
    --cc=rubini@unipv.it \
    --cc=ryan@bluewatersys.com \
    --cc=srinidhi.kasagar@stericsson.com \
    --cc=support@simtec.co.uk \
    --cc=tony@atomide.com \
    --cc=viresh.kumar@st.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;
as well as URLs for NNTP newsgroup(s).