linux-kernel - Re: [PATCH v3 0/6] ARM: ep93xx: ts72xx: Add support for BK3 board

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>] [day] [month] [year] [list]

Message-ID: <CAK8P3a2KQ7VK230yQ8NL2n0B-2eZhWrVFTTcAqJ_nT2gjg1nPg@mail.gmail.com>
Date:   Thu, 30 Nov 2017 11:44:39 +0100
From:   Arnd Bergmann <arnd@...db.de>
To:     Alexander Sverdlin <alexander.sverdlin@...il.com>
Cc:     Lukasz Majewski <lukma@...x.de>,
        Hartley Sweeten <hsweeten@...ionengravers.com>,
        Russell King <linux@...linux.org.uk>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Olof Johansson <olof@...om.net>,
        Linus Walleij <linus.walleij@...aro.org>
Subject: Re: [PATCH v3 0/6] ARM: ep93xx: ts72xx: Add support for BK3 board

On Thu, Nov 30, 2017 at 10:57 AM, Alexander Sverdlin
<alexander.sverdlin@...il.com> wrote:
> Hello Arnd!
>
> On Thu Nov 30 10:02:26 2017 Arnd Bergmann <arnd@...db.de> wrote:
>> Can we clarify who is picking up ep93xx patches these days? The
>> last time I think Linus Walleij offered to do it for the 4.14 merge
>> window, as neither Hartley nor Alexander had a git tree.
>>
>> I don't care too much who does it in the end, between Hartley, Alexander,
>> Linus and even Lukasz directly, but I'd like whoever feels responsible
>> for the platform to be listed in the MAINTAINERS file and pick up
>> the patches from everyone else to forward them to me as either
>> pull requests or separate patches to arm@...nel.org when the
>> patches are ready, so I don't have to make a decision about when to
>> pick them up from the list.
>
> As I stepped in as a maintainer there was a common understanding, that
> ep93xx is so inactive these days, that is doesn't deserve a separate tree.
> But I feel also that we will benefit from one, so let me create one this
> evening and I'll send you pull request when we agree with Lukasz.
> Just let me know if you'd be fine with github or should I care about
> kernel.org?

Up to you. Normally I try to avoid github for more active trees, but
if you don't already have kernel.org account, it's probably not worth
the effort of getting one just for the few ep93xx patches. As I said,
we're probably also fine with picking up the patches individually,
as long as the process is clear to everyone, i.e. you pick up the
patches from any other contributors and notify them about the
status of their patches, and then you send them to arm@...nel.org
in whatever way makes most sense for you.

       Arnd