From: Florian Fainelli <f.fainelli@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
open list <linux-kernel@vger.kernel.org>,
Shaokun Zhang <zhangshaokun@hisilicon.com>,
rmk+kernel@armlinux.org.uk
Subject: [PATCH v2 0/2] ARM/ARM64: Move cpu_logical_map[] to smp.h
Date: Mon, 3 Jun 2019 16:18:28 -0700 [thread overview]
Message-ID: <20190603231830.24129-1-f.fainelli@gmail.com> (raw)
Hi all,
These two patches make ARM and ARM64 consistent with other
architectures: sh, sparc, xtensa, mips, etc. to define cpu_logical_map
under asm/smp.h, which is included by linux/smp.h. This allows other
pieces of code like irqchip drivers to get access to cpu_logical_map[]
using linux/smp.h.
Changes in v2:
- just move __cpu_logical_map[]/cpu_logical_map[] to smp.h
Florian Fainelli (2):
arm64: smp: Moved cpu_logical_map[] to smp.h
ARM: smp: Moved cpu_logical_map[] to smp.h
arch/arm/include/asm/smp.h | 6 ++++++
arch/arm/include/asm/smp_plat.h | 5 -----
arch/arm64/include/asm/smp.h | 6 ++++++
arch/arm64/include/asm/smp_plat.h | 5 -----
4 files changed, 12 insertions(+), 10 deletions(-)
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-06-03 23:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 23:18 Florian Fainelli [this message]
2019-06-03 23:18 ` [PATCH v2 1/2] arm64: smp: Moved cpu_logical_map[] to smp.h Florian Fainelli
2019-06-05 12:09 ` Will Deacon
2019-06-07 17:18 ` Florian Fainelli
2019-06-03 23:18 ` [PATCH v2 2/2] ARM: " Florian Fainelli
2019-06-21 7:57 ` Russell King - ARM Linux admin
2019-06-21 14:46 ` Florian Fainelli
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=20190603231830.24129-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=will.deacon@arm.com \
--cc=zhangshaokun@hisilicon.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).