[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a1=GTcgbqkwnzsFtBtFZTtf4Lop7U5hsCAid-fCgs07yQ@mail.gmail.com>
Date: Tue, 14 Sep 2021 17:26:10 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Daniel Palmer <daniel@...f.com>
Cc: Arnd Bergmann <arnd@...db.de>,
Romain Perier <romain.perier@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Olof Johansson <olof@...om.net>, SoC Team <soc@...nel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
DTML <devicetree@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 4/4] MAINTAINERS: Add myself as MStar/Sigmastar Armv7 SoC maintainers
On Tue, Sep 14, 2021 at 5:03 PM Daniel Palmer <daniel@...f.com> wrote:
> On Tue, 14 Sept 2021 at 22:54, Arnd Bergmann <arnd@...db.de> wrote:
> > FWIW, I'd suggest merging the MAINTAINERS file change as a
> > bugfix for 5.15, it's generally better to do these as early as possible
> > to make sure any patches reach all the right people.
>
> That makes sense.
> Would it be possible for you to merge that single commit for me?
Done, merged into arm/fixes.
> Seems like that would be easier than me creating a fixes branch for a
> single commit, sending you a PR, finding out I still don't actually
> know how to do PR properly.. :)
> If it's a hassle I'll do the PR though.
If you only have one or two patches, sending that patch to soc@...nel.org
is usually the easiest way anyway, unless there is a reason to keep the
branch description separate from the patch description in the git log.
Arnd
Powered by blists - more mailing lists