public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: Andre Przywara <andre.przywara@arm.com>,
	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, 04 Jan 2016 13:12:53 +0100	[thread overview]
Message-ID: <12966735.VQfHhlD3ne@wuerfel> (raw)
In-Reply-To: <20160104112648.GD11722@lukather>

On Monday 04 January 2016 12:26:48 Maxime Ripard wrote:
> 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 usually take these through arm-soc. 
 
> We should also probably extend the MAINTAINERS entry, shouldn't we?
> 

A lot of the arm64 changes get sent to arm-soc from random developers that
are not in the MAINTAINERS file at the moment, and I'd like to reduce
that, so please pick up whatever arm64 sunxi changes you see that look ok
and send a separate pull request as you do for arm32. Sending patches
separately is fine too, but I'd like to see them come from you to arm@kernel.org
so I don't need to guess whether we should pick them up or not.

This time around, we have two arm64 branches, one for boot/dts and one
combined for Kconfig and defconfig (MAINTAINERS can also go in there). We
are still experimenting with that model though, and it may change in
the future.

	Arnd

  reply	other threads:[~2016-01-04 12:13 UTC|newest]

Thread overview: 20+ 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 ` [RFC PATCH 1/5] drivers: sunxi-rsb: fix error output type Andre Przywara
2015-12-22 22:02   ` Arnd Bergmann
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 22:06   ` Arnd Bergmann
2015-12-23  0:07     ` André Przywara
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 22:07   ` Arnd Bergmann
2015-12-24 12:56   ` Corentin LABBE
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 22:08   ` Arnd Bergmann
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 22:09   ` Arnd Bergmann
2016-01-04 11:26   ` Maxime Ripard
2016-01-04 12:12     ` Arnd Bergmann [this message]
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=12966735.VQfHhlD3ne@wuerfel \
    --to=arnd@arndb.de \
    --cc=andre.przywara@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=marc.zyngier@arm.com \
    --cc=maxime.ripard@free-electrons.com \
    --cc=wens@csie.org \
    --cc=will.deacon@arm.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