public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Pull request: removal of most instances of mach/memory.h
Date: Mon, 26 Sep 2011 23:38:10 +0100	[thread overview]
Message-ID: <20110926223810.GA23680@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.00.1109261514330.2718@xanadu.home>

On Mon, Sep 26, 2011 at 04:00:11PM -0400, Nicolas Pitre wrote:
> On Mon, 26 Sep 2011, Russell King - ARM Linux wrote:
> 
> > On Mon, Sep 26, 2011 at 10:33:28AM -0400, Nicolas Pitre wrote:
> > >       ARM: mach-ep93xx: remove mach/memory.h and Kconfig selection of SDRAM bank
> > 
> > Are you planning to totally kill off ZBOOT_ROM too?  Because removing
> > the zreladdr stuff is doing exactly that.
> 
> It looks like ZBOOT_ROM is not used on that platform at all.  However, 
> the ability to have a single defconfig and binary for the whole platform 
> is something that the mach-ep93xx maintainers are looking for.  Having 
> ZBOOT_ROM depend on and use CONFIG_PHYS_OFFSET would probably makes 
> sense eventually.

You miss the point.  Removing zreladdr actively _prevents_ anyone from
then choosing to build a kernel with ZBOOT_ROM enabled targetted for one
platform if that's what they want, because the decompressor then loses
the information it needs to properly locate the kernel.

> > This also gives additional merge conflicts elsewhere, and while git
> > rerere makes some of them easy, the quantity is going to be a right
> > pain to deal with on a repeated basis.
> 
> Again, I'm perfectly willing to use a different base for this series and 
> fix the conflicts myself if you give me one.

That's difficult when there are a number of unstable branches involved.

  parent reply	other threads:[~2011-09-26 22:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-07  3:13 Pull request: removal of most instances of mach/memory.h Nicolas Pitre
2011-09-13 12:50 ` Nicolas Pitre
2011-09-20 17:53   ` Nicolas Pitre
2011-09-26 13:15     ` Russell King - ARM Linux
2011-09-26 13:58       ` Nicolas Pitre
2011-09-26 14:33         ` Nicolas Pitre
2011-09-26 19:10           ` Russell King - ARM Linux
2011-09-26 20:00             ` Nicolas Pitre
2011-09-26 20:10               ` Nicolas Pitre
2011-09-26 22:38                 ` Russell King - ARM Linux
2011-09-26 23:03                   ` Nicolas Pitre
2011-09-26 23:29                     ` Russell King - ARM Linux
2011-09-27  0:40                       ` Nicolas Pitre
2011-09-27  0:52                         ` Nicolas Pitre
2011-09-27  7:21                           ` Russell King - ARM Linux
2011-09-27 12:31                             ` Nicolas Pitre
2011-09-26 22:38               ` Russell King - ARM Linux [this message]
2011-09-26 23:01                 ` Nicolas Pitre
2011-09-26 23:18                   ` Russell King - ARM Linux
2011-09-26 23:32                     ` Nicolas Pitre
2011-10-04 18:54             ` Nicolas Pitre
2011-10-17  0:48               ` Nicolas Pitre

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=20110926223810.GA23680@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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