From: Daniel Palmer <daniel@0x0f.com> To: Arnd Bergmann <arnd@arndb.de> Cc: 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: Wed, 15 Sep 2021 00:04:44 +0900 [thread overview] Message-ID: <CAFr9PXkipBnVDBOpdYhUD4bYNaL8qybPhGJi7YwSHaCNrPz6rw@mail.gmail.com> (raw) Message-ID: <20210914150444.KCVx_MJa2Vc8LA3wb1jkWhLtrwkAWTIfN0saCXwQTn4@z> (raw) In-Reply-To: <CAK8P3a24NTmkyh01OEzDQ8=oTWpUnDtwWQgUUxUbW2wxsgAFeA@mail.gmail.com> Hi Arnd, On Tue, 14 Sept 2021 at 22:54, Arnd Bergmann <arnd@arndb.de> wrote: > Sounds good to me. > > One process issue though: These emails were sent 'cc:soc@kernel.org', so > they end up in patchwork, but I'm guessing they were not actually meant > for us to apply from there. I'm happy to take merge these patches (or > a future version of the series) directly from patchwork if that's what you > both had in mind, but for clarity please either > > a) drop soc@kernel.org from Cc for patches that are meant for review > and will be part of a pull request. > > or > > b) put soc@kernel.org in the 'to:' field after they have been reviewed > and you want them to get merged. Noted for the future. Until now we haven't done pull requests so having the patches go into the soc patchwork made sense but from now on we'll send pull requests when needed to you and Olof for the ARM specific bits. Which I don't think there will be much aside from dts stuff. > Or even better, add an explicit sentence below the '---' line asking > for the patches to be merged directly into the soc tree when this > is what you want. Noted. > 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? 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. Cheers, Daniel _______________________________________________ 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: Daniel Palmer <daniel@0x0f.com> To: Arnd Bergmann <arnd@arndb.de> Cc: 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: Wed, 15 Sep 2021 00:04:44 +0900 [thread overview] Message-ID: <CAFr9PXkipBnVDBOpdYhUD4bYNaL8qybPhGJi7YwSHaCNrPz6rw@mail.gmail.com> (raw) Message-ID: <20210914150444.Ow7zEPfkhJUJw6tnwIm1OWBFZqGz1jctK9d2UzmZXbA@z> (raw) In-Reply-To: <CAK8P3a24NTmkyh01OEzDQ8=oTWpUnDtwWQgUUxUbW2wxsgAFeA@mail.gmail.com> Hi Arnd, On Tue, 14 Sept 2021 at 22:54, Arnd Bergmann <arnd@arndb.de> wrote: > Sounds good to me. > > One process issue though: These emails were sent 'cc:soc@kernel.org', so > they end up in patchwork, but I'm guessing they were not actually meant > for us to apply from there. I'm happy to take merge these patches (or > a future version of the series) directly from patchwork if that's what you > both had in mind, but for clarity please either > > a) drop soc@kernel.org from Cc for patches that are meant for review > and will be part of a pull request. > > or > > b) put soc@kernel.org in the 'to:' field after they have been reviewed > and you want them to get merged. Noted for the future. Until now we haven't done pull requests so having the patches go into the soc patchwork made sense but from now on we'll send pull requests when needed to you and Olof for the ARM specific bits. Which I don't think there will be much aside from dts stuff. > Or even better, add an explicit sentence below the '---' line asking > for the patches to be merged directly into the soc tree when this > is what you want. Noted. > 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? 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. Cheers, Daniel
next prev parent reply other threads:[~2021-09-14 15:04 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 [this message] 2021-09-14 15:04 ` Daniel Palmer [not found] ` <20210914152610.naiVsGyusiPbf9b_3tTofLoTeN2hYqpowPYkjGvi4gw@z> 2021-09-14 15:26 ` Arnd Bergmann 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=CAFr9PXkipBnVDBOpdYhUD4bYNaL8qybPhGJi7YwSHaCNrPz6rw@mail.gmail.com \ --to=daniel@0x0f.com \ --cc=arnd@arndb.de \ --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: linkBe 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).