lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 13 May 2015 16:00:21 +0900
From:	Masahiro Yamada <yamada.masahiro@...ionext.com>
To:	Arnd Bergmann <arnd@...db.de>, arm@...nel.org
Cc:	Olof Johansson <olof@...om.net>, devicetree@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v7 0/4] ARM: SoC: add a new platform, UniPhier (arch/arm/mach-uniphier)

Hi Arnd,


2015-05-13 0:00 GMT+09:00 Arnd Bergmann <arnd@...db.de>:
> On Friday 08 May 2015 13:07:10 Masahiro Yamada wrote:
>> This is an initial series for supporting Socionext UniPhier SoCs,
>> based on ARM Cortex-A9, mainly used for digital TVs, video recorders, etc.
>>
>>
>> Masahiro Yamada (4):
>>   ARM: UniPhier: add basic support for UniPhier architecture
>>   ARM: multi_v7_defconfig: enable UniPhier SoC family
>>   ARM: dts: UniPhier: add support for UniPhier SoCs and boards
>>   MAINTAINERS: add myself as ARM/UniPhier maintainer
>
> Applied all four patches, to the next/soc, next/defconfig, next/dt and
> next/soc branches respectively.

Thanks!
I can see them.


> Welcome as our latest new maintainer. In the future, please send
> any follow-up patches for the architecture specific code to
> arm@...nel.org in addition to the normal recipients, once you
> consider them ready to be applied.


Please teach me a little more because I am not experienced enough
in this community.


I checked MAINTAINERS, but I could not find arm@...nel.org.
Is it documented somewhere?

I found ARM SUB-ARCHITECTURES entry in that file, but it does not mention
the responsible individuals.
(I assume, you and Olof are the ones.)


ARM SUB-ARCHITECTURES
L:      linux-arm-kernel@...ts.infradead.org (moderated for non-subscribers)
S:      Maintained
F:      arch/arm/mach-*/
F:      arch/arm/plat-*/
T:      git git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git



I have one more question.

Are you receiving pull requests from each sub-arch maintainer?
Or should every patch be submitted to arm@...nel.org and
applied by you (or other ARM-SoC maintainers)?

I have not earned enough reputations in this ML, so I know
it is too early for me to handle pull-reqs.

I understand the general development process of Linux, but
the maintainership of the ARM-SoC subsystem looks more hierarchized, so
I just want to know its development process correctly.


-- 
Best Regards
Masahiro Yamada
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ