From: Arnd Bergmann <arnd@arndb.de>
To: Daniel Palmer <daniel@0x0f.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Romain Perier <romain.perier@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Olof Johansson <olof@lixom.net>, SoC Team <soc@kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
DTML <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/4] MAINTAINERS: Add myself as MStar/Sigmastar Armv7 SoC maintainers
Date: Tue, 14 Sep 2021 17:26:10 +0200 [thread overview]
Message-ID: <CAK8P3a1=GTcgbqkwnzsFtBtFZTtf4Lop7U5hsCAid-fCgs07yQ@mail.gmail.com> (raw)
Message-ID: <20210914152610.naiVsGyusiPbf9b_3tTofLoTeN2hYqpowPYkjGvi4gw@z> (raw)
In-Reply-To: <CAFr9PXkipBnVDBOpdYhUD4bYNaL8qybPhGJi7YwSHaCNrPz6rw@mail.gmail.com>
On Tue, Sep 14, 2021 at 5:03 PM Daniel Palmer <daniel@0x0f.com> wrote:
> On Tue, 14 Sept 2021 at 22:54, Arnd Bergmann <arnd@arndb.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@kernel.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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Daniel Palmer <daniel@0x0f.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Romain Perier <romain.perier@gmail.com>,
Rob Herring <robh+dt@kernel.org>, Olof Johansson <olof@lixom.net>,
SoC Team <soc@kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
DTML <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/4] MAINTAINERS: Add myself as MStar/Sigmastar Armv7 SoC maintainers
Date: Tue, 14 Sep 2021 17:26:10 +0200 [thread overview]
Message-ID: <CAK8P3a1=GTcgbqkwnzsFtBtFZTtf4Lop7U5hsCAid-fCgs07yQ@mail.gmail.com> (raw)
Message-ID: <20210914152610.tLlLNKtcCavHT4jHT5nr9WK4SiWz7k0LGibywl9MVUA@z> (raw)
In-Reply-To: <CAFr9PXkipBnVDBOpdYhUD4bYNaL8qybPhGJi7YwSHaCNrPz6rw@mail.gmail.com>
On Tue, Sep 14, 2021 at 5:03 PM Daniel Palmer <daniel@0x0f.com> wrote:
> On Tue, 14 Sept 2021 at 22:54, Arnd Bergmann <arnd@arndb.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@kernel.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
next prev parent reply other threads:[~2021-09-14 15:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210910190318.LiBVdGxNtTh1STWT7X-D6-ycVsuAIw2eGokZ2mGkwHQ@z>
2021-09-10 19:03 ` [PATCH 0/4] Add support for IDO-SBC2D06-V1B-22W Romain Perier
[not found] ` <20210910190319.-W3JSWMF-ViH0xEBABZu9QxYXYsqAMCcnUzaQOuA0VA@z>
2021-09-10 19:03 ` [PATCH 1/4] ARM: mstar: Mark timer with arm, cpu-registers-not-fw-configured Romain Perier
[not found] ` <20210910190320.I83Fh3D9fot2qvtxilXNNe69lepFYpFNP_UhnJbwApA@z>
2021-09-10 19:03 ` [PATCH 2/4] ARM: dts: mstar: Add the Wireless Tag IDO-SBC2D06-V1B-22W Romain Perier
[not found] ` <20210911031832.Cbmi2AFC5itpE51xSVUVcaU38zhQIv6qXNdVfFo7ioE@z>
2021-09-11 3:18 ` Daniel Palmer
2021-09-11 3:18 ` Daniel Palmer
[not found] ` <20210911121953.mlR9YmwioU31zCrhfzJJ30Nc146d4Zpow05SFhNnseg@z>
2021-09-11 12:19 ` Romain Perier
2021-09-11 12:19 ` Romain Perier
[not found] ` <20210910190321.VxpWTm8epkxLaAggLaakGNK5-Y-sx7hgd4Ljxr_UrA0@z>
2021-09-10 19:03 ` [PATCH 3/4] dt-bindings: add vendor prefix for Wireless Tag Romain Perier
2021-09-11 2:49 ` Daniel Palmer
[not found] ` <20210911025921.UtZhdDpABm5BJya3ddE8il1-rQQrQnCPy8lf195ECQc@z>
2021-09-11 2:59 ` Daniel Palmer
2021-09-11 2:59 ` Daniel Palmer
[not found] ` <20210911122058.1QibK7bSO8D1CnKmHwsH_7kMRLwBwVaKeULAbmLi3_M@z>
2021-09-11 12:20 ` Romain Perier
2021-09-11 12:20 ` Romain Perier
[not found] ` <20210910190322.cLx5d5PXwwjgl_MbuGLEVO8AAmxCkVtVgXIr5kqrZPM@z>
2021-09-10 19:03 ` [PATCH 4/4] MAINTAINERS: Add myself as MStar/Sigmastar Armv7 SoC maintainers Romain Perier
[not found] ` <20210911025633.pjXagSIKnRktvUFq3FZOzk7DaWlktUgXHO0pzS2yYsk@z>
2021-09-11 2:56 ` Daniel Palmer
2021-09-11 2:56 ` Daniel Palmer
[not found] ` <20210914135404.sU3SgUIVmXy-eKlMo7YpzMEaOxhI3idFIzhgE0HY_RM@z>
2021-09-14 13:54 ` Arnd Bergmann
2021-09-14 13:54 ` Arnd Bergmann
[not found] ` <20210914150444.KCVx_MJa2Vc8LA3wb1jkWhLtrwkAWTIfN0saCXwQTn4@z>
2021-09-14 15:04 ` Daniel Palmer
2021-09-14 15:04 ` Daniel Palmer
[not found] ` <20210914152610.naiVsGyusiPbf9b_3tTofLoTeN2hYqpowPYkjGvi4gw@z>
2021-09-14 15:26 ` Arnd Bergmann [this message]
2021-09-14 15:26 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAK8P3a1=GTcgbqkwnzsFtBtFZTtf4Lop7U5hsCAid-fCgs07yQ@mail.gmail.com' \
--to=arnd@arndb.de \
--cc=daniel@0x0f.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=romain.perier@gmail.com \
--cc=soc@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).