From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 5/5] arm64: Introduce Allwinner SoC config option
Date: Mon, 4 Jan 2016 12:26:48 +0100 [thread overview]
Message-ID: <20160104112648.GD11722@lukather> (raw)
In-Reply-To: <1450787267-26836-6-git-send-email-andre.przywara@arm.com>
Hi Andre, Arnd,
On Tue, Dec 22, 2015 at 12:27:47PM +0000, Andre Przywara wrote:
> To prepare for supporting the Allwinner A64 SoC, introduce a config
> option to allow compiling Allwinner (aka. sunxi) specific drivers
> for ARM64.
> This patch just defines the ARCH_SUNXI symbol to allow Allwinner
> specific drivers to be selected during kernel configuration.
>
> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
I'm ok taking this patch.
I'm not quite sure how the process works though with arm64. Should I
send a PR with this patch to Catalin, or does it go through the usual
arm-soc maintainers?
We should also probably extend the MAINTAINERS entry, shouldn't we?
Thanks,
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160104/3fa8d2eb/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: arnd@arndb.de, Andre Przywara <andre.przywara@arm.com>
Cc: Chen-Yu Tsai <wens@csie.org>,
marc.zyngier@arm.com, catalin.marinas@arm.com,
will.deacon@arm.com, linux-sunxi@googlegroups.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 5/5] arm64: Introduce Allwinner SoC config option
Date: Mon, 4 Jan 2016 12:26:48 +0100 [thread overview]
Message-ID: <20160104112648.GD11722@lukather> (raw)
In-Reply-To: <1450787267-26836-6-git-send-email-andre.przywara@arm.com>
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
Hi Andre, Arnd,
On Tue, Dec 22, 2015 at 12:27:47PM +0000, Andre Przywara wrote:
> To prepare for supporting the Allwinner A64 SoC, introduce a config
> option to allow compiling Allwinner (aka. sunxi) specific drivers
> for ARM64.
> This patch just defines the ARCH_SUNXI symbol to allow Allwinner
> specific drivers to be selected during kernel configuration.
>
> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
I'm ok taking this patch.
I'm not quite sure how the process works though with arm64. Should I
send a PR with this patch to Catalin, or does it go through the usual
arm-soc maintainers?
We should also probably extend the MAINTAINERS entry, shouldn't we?
Thanks,
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-01-04 11:26 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 12:27 [RFC PATCH 0/5] arm64: prepare for basic Allwinner support Andre Przywara
2015-12-22 12:27 ` Andre Przywara
2015-12-22 12:27 ` [RFC PATCH 1/5] drivers: sunxi-rsb: fix error output type Andre Przywara
2015-12-22 12:27 ` Andre Przywara
2015-12-22 22:02 ` Arnd Bergmann
2015-12-22 22:02 ` Arnd Bergmann
2015-12-27 22:03 ` Maxime Ripard
2015-12-27 22:03 ` Maxime Ripard
2015-12-22 12:27 ` [RFC PATCH 2/5] crypto: sunxi-ss: fix min3() call to match types Andre Przywara
2015-12-22 12:27 ` Andre Przywara
[not found] ` <1450787267-26836-3-git-send-email-andre.przywara-5wv7dgnIgG8@public.gmane.org>
2015-12-22 22:06 ` Arnd Bergmann
2015-12-22 22:06 ` Arnd Bergmann
2015-12-22 22:06 ` Arnd Bergmann
[not found] ` <201512222306.58681.arnd-r2nGTMty4D4@public.gmane.org>
2015-12-23 0:07 ` André Przywara
2015-12-23 0:07 ` André Przywara
2015-12-23 0:07 ` André Przywara
2016-01-04 14:20 ` Uwe Kleine-König
2016-01-04 14:20 ` Uwe Kleine-König
2015-12-22 12:27 ` [RFC PATCH 3/5] crypto: sunxi-ss: fix dev_dbg() output type Andre Przywara
2015-12-22 12:27 ` Andre Przywara
[not found] ` <1450787267-26836-4-git-send-email-andre.przywara-5wv7dgnIgG8@public.gmane.org>
2015-12-22 22:07 ` Arnd Bergmann
2015-12-22 22:07 ` Arnd Bergmann
2015-12-22 22:07 ` Arnd Bergmann
2015-12-24 12:56 ` Corentin LABBE
2015-12-24 12:56 ` Corentin LABBE
2015-12-24 12:56 ` Corentin LABBE
2015-12-27 22:05 ` Maxime Ripard
2015-12-27 22:05 ` Maxime Ripard
2015-12-22 12:27 ` [RFC PATCH 4/5] irqchip: sun4i: fix compilation outside of arch/arm Andre Przywara
2015-12-22 12:27 ` Andre Przywara
2015-12-22 22:08 ` Arnd Bergmann
2015-12-22 22:08 ` Arnd Bergmann
2015-12-27 22:04 ` Maxime Ripard
2015-12-27 22:04 ` Maxime Ripard
2015-12-22 12:27 ` [RFC PATCH 5/5] arm64: Introduce Allwinner SoC config option Andre Przywara
2015-12-22 12:27 ` Andre Przywara
2015-12-22 22:09 ` Arnd Bergmann
2015-12-22 22:09 ` Arnd Bergmann
2016-01-04 11:26 ` Maxime Ripard [this message]
2016-01-04 11:26 ` Maxime Ripard
2016-01-04 12:12 ` Arnd Bergmann
2016-01-04 12:12 ` Arnd Bergmann
2016-01-06 21:03 ` Maxime Ripard
2016-01-06 21:03 ` Maxime Ripard
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=20160104112648.GD11722@lukather \
--to=maxime.ripard@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.