linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mm: pull asm/memory.h explicitly
Date: Thu, 18 Aug 2016 16:11:35 +0100	[thread overview]
Message-ID: <20160818151135.GC1041@n2100.armlinux.org.uk> (raw)
In-Reply-To: <57B5C6FD.1090104@arm.com>

On Thu, Aug 18, 2016 at 03:32:29PM +0100, Vladimir Murzin wrote:
> On 18/08/16 15:22, Russell King - ARM Linux wrote:
> > On Wed, Aug 17, 2016 at 05:17:14PM +0100, Vladimir Murzin wrote:
> >> Commit d78114554939a (""ARM: 8512/1: proc-v7.S: Adjust stack address when
> >> XIP_KERNEL"") introduced a macro which lives under asm/memory.h.
> >> Unfortunately, for MMU-less systems (like R-class) it leads to build failure:
> >>
> >> arch/arm/mm/proc-v7.S: Assembler messages:
> >> arch/arm/mm/proc-v7.S:538: Error: unrecognised relocation suffix
> >> make[1]: *** [arch/arm/mm/proc-v7.o] Error 1
> >> make: *** [arch/arm/mm] Error 2
> >>
> >> since it is implicitly pulled via asm/pgtable.h for MMU capable systems only.
> >>
> >> To fix it include asm/memory.h explicitly.
> >>
> >> Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com>
> > 
> > Looks fine, thanks.
> > 
> 
> Should I drop it into patch system?

Yes please.

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

      reply	other threads:[~2016-08-18 15:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-17 16:17 [PATCH] ARM: mm: pull asm/memory.h explicitly Vladimir Murzin
2016-08-18 14:22 ` Russell King - ARM Linux
2016-08-18 14:32   ` Vladimir Murzin
2016-08-18 15:11     ` Russell King - ARM Linux [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=20160818151135.GC1041@n2100.armlinux.org.uk \
    --to=linux@armlinux.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;
as well as URLs for NNTP newsgroup(s).