[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151222171158.GD1302@e104818-lin.cambridge.arm.com>
Date: Tue, 22 Dec 2015 17:11:59 +0000
From: Catalin Marinas <catalin.marinas@....com>
To: Yury Norov <ynorov@...iumnetworks.com>
Cc: arnd@...db.de, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, pinskia@...il.com,
Prasun.Kapoor@...iumnetworks.com, schwab@...e.de,
broonie@...nel.org, Nathan_Lynch@...tor.com, agraf@...e.de,
klimov.linux@...il.com, jan.dakinevich@...il.com,
ddaney.cavm@...il.com, bamvor.zhangjian@...wei.com,
philipp.tomsich@...obroma-systems.com, joseph@...esourcery.com,
christoph.muellner@...obroma-systems.com
Subject: Re: [PATCH v6 15/20] arm64: signal: move ilp32 and lp64 common code
to separated file
On Wed, Dec 16, 2015 at 12:42:41AM +0300, Yury Norov wrote:
> After that, it will be possible to reuse it in ILP32.
>
> Signed-off-by: Yury Norov <ynorov@...iumnetworks.com>
> ---
> arch/arm64/include/asm/signal_common.h | 39 ++++++++
> arch/arm64/kernel/Makefile | 2 +-
> arch/arm64/kernel/signal.c | 154 +----------------------------
> arch/arm64/kernel/signal_common.c | 174 +++++++++++++++++++++++++++++++++
signal.c is always compiled, so I don't see the point of a
signal_common.c, just export the functions from signal.c
(signal32_common.c is a different story since we may not always compile
AArch32 support in).
--
Catalin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists