Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1311474 > unrolled thread

Re: [PATCH v7 0/4] ARM: SoC: add a new platform, UniPhier (arch/arm/mach-uniphier)

Started byMasahiro Yamada <yamada.masahiro@socionext.com>
First post2016-01-18 12:00 +0100
Last post2016-01-18 15:00 +0100
Articles 2 — 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.


Contents

  Re: [PATCH v7 0/4] ARM: SoC: add a new platform, UniPhier (arch/arm/mach-uniphier) Masahiro Yamada <yamada.masahiro@socionext.com> - 2016-01-18 12:00 +0100
    Re: [PATCH v7 0/4] ARM: SoC: add a new platform, UniPhier (arch/arm/mach-uniphier) Arnd Bergmann <arnd@arndb.de> - 2016-01-18 15:00 +0100

#1311474 — Re: [PATCH v7 0/4] ARM: SoC: add a new platform, UniPhier (arch/arm/mach-uniphier)

FromMasahiro Yamada <yamada.masahiro@socionext.com>
Date2016-01-18 12:00 +0100
SubjectRe: [PATCH v7 0/4] ARM: SoC: add a new platform, UniPhier (arch/arm/mach-uniphier)
Message-ID<qSfHs-7W3-3@gated-at.bofh.it>
Hi Arnd,


2015-05-13 16:48 GMT+09:00 Arnd Bergmann <arnd@arndb.de>:
> On Wednesday 13 May 2015 16:00:21 Masahiro Yamada wrote:
>> 2015-05-13 0:00 GMT+09:00 Arnd Bergmann <arnd@arndb.de>:
>> > On Friday 08 May 2015 13:07:10 Masahiro Yamada wrote:
>> > Welcome as our latest new maintainer. In the future, please send
>> > any follow-up patches for the architecture specific code to
>> > arm@kernel.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@kernel.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.)
>>
>
> We normally only take patches from subarch maintainers that know who
> we are and how it works, but we don't want to be Cc'd on every single
> patch, so we don't have an entry in MAINTAINERS directly.
>
>> I have one more question.
>>
>> Are you receiving pull requests from each sub-arch maintainer?
>> Or should every patch be submitted to arm@kernel.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.
>
> No worries, if you are unsure you can always ask us on the mailing
> list or on the #armlinux channel on irc.freenode.net.
>
> If you have more than a few patches at once, we'd always appreciate
> a pull request, for a couple of patches, emails to arm@kernel.org plus
> linux-arm-kernel are fine as well.
>
> When you do pull requests, please split them up according to larger
> topics, e.g. send dts changes separately from code changes, and
> separate bug fixes, cleanups and new feature support.
>
> Often when you add a new driver, that will require sending the driver
> code to a subsystem maintainer, and the dts changes to us. If everything
> goes well, your DT bindings are both forward and backward compatible,
> so they can get merged independently. If you ever have interdependencies
> between them, talk to us first so we can find a solution.
>
> For sending pull requests, it would be good to have a gpg key that
> is signed by other well-known kernel developers. If you have such
> a key, you can also request a kernel.org account to host a git tree
> there, or you can host a git tree somewhere on your company's domain.
> A public hosting service like github is not as good for us, but we
> can deal with it when you are still ramping up your infrastructure.
> Let me know if you need help finding kernel developers to sign your key.
>
>         Arnd


About 7 months have passed since I became a sub-arch maintainer (ARM/UniPhier),
and I am hoping now I deserve to have the gpg key thing you mentioned.

Could you help me get a key and a kernel.org account to host a git tree?

It would make it easier to get SoC-specific things in
without loading you and Olof.



-- 
Best Regards
Masahiro Yamada

[toc] | [next] | [standalone]


#1311563

FromArnd Bergmann <arnd@arndb.de>
Date2016-01-18 15:00 +0100
Message-ID<qSivE-1pl-3@gated-at.bofh.it>
In reply to#1311474
On Monday 18 January 2016 19:54:08 Masahiro Yamada wrote:
> 2015-05-13 16:48 GMT+09:00 Arnd Bergmann <arnd@arndb.de>:
> > On Wednesday 13 May 2015 16:00:21 Masahiro Yamada wrote:
> >
> > No worries, if you are unsure you can always ask us on the mailing
> > list or on the #armlinux channel on irc.freenode.net.
> >
> > If you have more than a few patches at once, we'd always appreciate
> > a pull request, for a couple of patches, emails to arm@kernel.org plus
> > linux-arm-kernel are fine as well.
> >
> > When you do pull requests, please split them up according to larger
> > topics, e.g. send dts changes separately from code changes, and
> > separate bug fixes, cleanups and new feature support.
> >
> > Often when you add a new driver, that will require sending the driver
> > code to a subsystem maintainer, and the dts changes to us. If everything
> > goes well, your DT bindings are both forward and backward compatible,
> > so they can get merged independently. If you ever have interdependencies
> > between them, talk to us first so we can find a solution.
> >
> > For sending pull requests, it would be good to have a gpg key that
> > is signed by other well-known kernel developers. If you have such
> > a key, you can also request a kernel.org account to host a git tree
> > there, or you can host a git tree somewhere on your company's domain.
> > A public hosting service like github is not as good for us, but we
> > can deal with it when you are still ramping up your infrastructure.
> > Let me know if you need help finding kernel developers to sign your key.
> 
> 
> About 7 months have passed since I became a sub-arch maintainer (ARM/UniPhier),
> and I am hoping now I deserve to have the gpg key thing you mentioned.
> 
> Could you help me get a key and a kernel.org account to host a git tree?
> 
> It would make it easier to get SoC-specific things in
> without loading you and Olof.

Getting the kernel.org account should be straightforward once you have
a signed gpg key, see the description in https://www.kernel.org/category/faq.html

If you don't have a gpg key yet, please generate one with 4096 bits
keylength now. It's good to get as many signatures as possible from people
that already have signatures by other kernel contributors. The complication
is that you anyone who signs your key needs to verify your identity, otherwise
the signature method would not be helpful.

I have added three people to Cc that might be able you here: I understand that
you live in Osaka, so Simon Horman would be physically the closest in Kobe.
Takahiro Akashi works at Socionext in Tokyo, and I think you already know Akira
Tsukamoto.

If you happen to be in the same place with one of them, or maybe they have
already signed the key of someone close by.

	Arnd

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web