public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] DEBUG_LL platform updates for 3.2
Date: Wed, 12 Oct 2011 09:38:19 +0100	[thread overview]
Message-ID: <20111012083819.GB2418@totoro> (raw)
In-Reply-To: <alpine.LFD.2.02.1110111950290.17040@xanadu.home>

Hi Nicolas,

On Tue, Oct 11, 2011 at 08:03:38PM -0400, Nicolas Pitre wrote:
> On Tue, 11 Oct 2011, Arnd Bergmann wrote:
> 
> > I've stuck them into the arm-soc tree for now, so we get linux-next
> > coverage, but I won't send them to Linus this way because then we
> > would get the same commits twice in the history.
> 
> Could you please do the same with the following:
> 
>   git://git.linaro.org/people/nico/linux.git mach_memory_h
> 
> Russell pulled it at some point, and dropped it due to concerns about 
> repeated conflict resolutions (or so I presume).  I just did a test 
> merge between your for-next branch and the above and that looked trivial 
> enough.

I just had a quick look at this branch as picoxcell has just been merged 
with an empty memory.h.  I'll submit a patch to remove that, but I just 
noticed in "ARM: switch from NO_MACH_MEMORY_H to NEED_MACH_MEMORY_H" 
there is this hunk:

diff --git a/arch/arm/plat-omap/Kconfig b/arch/arm/plat-omap/Kconfig
index e00fe76..6d49d2f1d 100644
--- a/arch/arm/plat-omap/Kconfig
+++ b/arch/arm/plat-omap/Kconfig
@@ -14,6 +14,7 @@ config ARCH_OMAP1
        select CLKDEV_LOOKUP
        select CLKSRC_MMIO
        select GENERIC_IRQ_CHIP
+       select HAVE_MACH_MEMORY_H
        help
          "Systems based on omap7xx, omap15xx or omap16xx"

and I think that should be "select NEED_MACH_MEMORY_H" instead.

Jamie

  parent reply	other threads:[~2011-10-12  8:38 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-28 10:38 [GIT PULL] DEBUG_LL platform updates for 3.2 Will Deacon
2011-10-03  8:35 ` Will Deacon
2011-10-07 20:51 ` Arnd Bergmann
2011-10-10 10:36   ` Will Deacon
2011-10-10 11:20     ` Arnd Bergmann
2011-10-10 13:32       ` Will Deacon
2011-10-11  7:52         ` Shawn Guo
2011-10-11 13:33         ` Arnd Bergmann
2011-10-11 15:09           ` Will Deacon
2011-10-11 18:48             ` Will Deacon
2011-10-11 19:25               ` Arnd Bergmann
2011-10-12  0:03                 ` Nicolas Pitre
2011-10-12  8:30                   ` Arnd Bergmann
2011-10-13  8:28                     ` Russell King - ARM Linux
2011-10-13 13:39                       ` Nicolas Pitre
2011-10-13 14:05                         ` Russell King - ARM Linux
2011-10-13 18:36                           ` Nicolas Pitre
2011-10-13 14:50                         ` Arnd Bergmann
2011-10-13 23:09                         ` Ryan Mallon
2011-10-13 23:40                           ` Ryan Mallon
2011-10-14  2:32                           ` Nicolas Pitre
2011-10-12  8:38                   ` Jamie Iles [this message]
2011-10-12 20:16                     ` Nicolas Pitre
2011-10-13  8:23                   ` Russell King - ARM Linux
2011-10-13 18:46                     ` Nicolas Pitre
2011-10-12 17:29                 ` Russell King - ARM Linux
2011-10-12 17:35                   ` Will Deacon
2011-10-12 18:01                     ` Russell King - ARM Linux
2011-10-12 18:05                       ` Will Deacon
2011-10-17  8:25                 ` Russell King - ARM Linux
2011-10-17  9:23                   ` Will Deacon
2011-10-20 14:57                     ` Arnd Bergmann
2011-10-21 10:59                       ` Will Deacon
2011-10-21 14:48                         ` Rob Herring
2011-10-21 15:11                           ` Arnd Bergmann
2011-10-21 15:15                           ` Will Deacon
2011-10-21 18:03                             ` Rob Herring
2011-10-21 23:04                               ` Rob Herring

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=20111012083819.GB2418@totoro \
    --to=jamie@jamieiles.com \
    --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