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] [day] [month] [year] [list]
Message-ID: <20200228115340.26495693@donnerap.cambridge.arm.com>
Date:   Fri, 28 Feb 2020 11:53:40 +0000
From:   Andre Przywara <andre.przywara@....com>
To:     Olof Johansson <olof@...om.net>
Cc:     Rob Herring <robh@...nel.org>,
        Linux ARM Mailing List <linux-arm-kernel@...ts.infradead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        DTML <devicetree@...r.kernel.org>,
        Maxime Ripard <mripard@...nel.org>,
        Robert Richter <rric@...nel.org>, SoC Team <soc@...nel.org>,
        Jon Loeliger <jdl@....com>,
        Mark Langsdorf <mlangsdo@...hat.com>,
        Eric Auger <eric.auger@...hat.com>,
        Will Deacon <will@...nel.org>,
        Catalin Marinas <catalin.marinas@....com>
Subject: Re: [PATCH v2 13/13] MAINTAINERS: Update Calxeda Highbank
 maintainership

On Thu, 27 Feb 2020 16:39:44 -0800
Olof Johansson <olof@...om.net> wrote:

> On Thu, Feb 27, 2020 at 2:35 PM Rob Herring <robh@...nel.org> wrote:
> >
> > On Thu, Feb 27, 2020 at 06:22:10PM +0000, Andre Przywara wrote:  
> > > Rob sees little point in maintaining the Calxeda architecture (early ARM
> > > 32-bit server) anymore.
> > > Since I have a machine sitting under my desk, change the maintainership
> > > to not lose support for that platform.
> > >
> > > Signed-off-by: Andre Przywara <andre.przywara@....com>
> > > ---
> > >  MAINTAINERS | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)  
> >
> > Acked-by: Rob Herring <robh@...nel.org>
> >
> > Send a PR to arm-soc folks for this and the dts changes. I'll pickup the
> > bindings.  
> 
> Given that it's likely to be a low volume of code, we can also just
> apply patches directly in this case (if it's easier than setting up a
> kernel.org account, etc). Andre, just let us know your preference.

I am happy (and more familiar) with just sending a final series via email. Especially if you insist on pulling from kernel.org git trees only, that is probably the only way for now.

To gain more independence from "corporate email" I am looking forward to setting up a kernel.org account and sending proper PRs in the future, but indeed this is probably overkill given the expected volume of patches.

Let me just run some test with the final version of the DT, then I will send a v3.

Cheers,
Andre


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ