Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1300648 > unrolled thread
| Started by | Maxime Ripard <maxime.ripard@free-electrons.com> |
|---|---|
| First post | 2016-01-04 12:30 +0100 |
| Last post | 2016-01-06 22:10 +0100 |
| Articles | 3 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [RFC PATCH 5/5] arm64: Introduce Allwinner SoC config option Maxime Ripard <maxime.ripard@free-electrons.com> - 2016-01-04 12:30 +0100
Re: [RFC PATCH 5/5] arm64: Introduce Allwinner SoC config option Arnd Bergmann <arnd@arndb.de> - 2016-01-04 13:20 +0100
Re: [RFC PATCH 5/5] arm64: Introduce Allwinner SoC config option Maxime Ripard <maxime.ripard@free-electrons.com> - 2016-01-06 22:10 +0100
| From | Maxime Ripard <maxime.ripard@free-electrons.com> |
|---|---|
| Date | 2016-01-04 12:30 +0100 |
| Subject | Re: [RFC PATCH 5/5] arm64: Introduce Allwinner SoC config option |
| Message-ID | <qNbuO-2MN-25@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
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
[toc] | [next] | [standalone]
| From | Arnd Bergmann <arnd@arndb.de> |
|---|---|
| Date | 2016-01-04 13:20 +0100 |
| Message-ID | <qNchc-3mS-11@gated-at.bofh.it> |
| In reply to | #1300648 |
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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [next] | [standalone]
| From | Maxime Ripard <maxime.ripard@free-electrons.com> |
|---|---|
| Date | 2016-01-06 22:10 +0100 |
| Message-ID | <qO3ve-6u0-39@gated-at.bofh.it> |
| In reply to | #1300691 |
[Multipart message — attachments visible in raw view] — view raw
Hi Arnd, On Mon, Jan 04, 2016 at 01:12:53PM +0100, Arnd Bergmann wrote: > 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. Ok. > > 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. Understood. Thanks a lot! Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web