LKML Archive on
help / color / mirror / Atom feed
From: Daniel Palmer <>
To: Arnd Bergmann <>
Cc: Romain Perier <>,
	Rob Herring <>, Olof Johansson <>,
	SoC Team <>,
	linux-arm-kernel <>,
	DTML <>,
	Linux Kernel Mailing List <>
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: <> (raw)
In-Reply-To: <>

Hi Arnd,

On Tue, 14 Sept 2021 at 22:54, Arnd Bergmann <> wrote:
> Sounds good to me.
> One process issue though: These emails were sent '', 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 from Cc for patches that are meant for review
> and will be part of a pull request.
> or
> b) put 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

> 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.


> 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.



  reply	other threads:[~2021-09-14 15:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-10 19:03 [PATCH 0/4] Add support for IDO-SBC2D06-V1B-22W Romain Perier
2021-09-10 19:03 ` [PATCH 1/4] ARM: mstar: Mark timer with arm,cpu-registers-not-fw-configured Romain Perier
2021-09-10 19:03 ` [PATCH 2/4] ARM: dts: mstar: Add the Wireless Tag IDO-SBC2D06-V1B-22W Romain Perier
2021-09-11  3:18   ` Daniel Palmer
2021-09-11 12:19     ` Romain Perier
2021-09-10 19:03 ` [PATCH 3/4] dt-bindings: add vendor prefix for Wireless Tag Romain Perier
2021-09-11  2:59   ` Daniel Palmer
2021-09-11 12:20     ` Romain Perier
2021-09-10 19:03 ` [PATCH 4/4] MAINTAINERS: Add myself as MStar/Sigmastar Armv7 SoC maintainers Romain Perier
2021-09-11  2:56   ` Daniel Palmer
2021-09-14 13:54     ` Arnd Bergmann
2021-09-14 15:04       ` Daniel Palmer [this message]
2021-09-14 15:26         ` Arnd Bergmann
2021-09-14 17:09           ` Romain Perier

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH 4/4] MAINTAINERS: Add myself as MStar/Sigmastar Armv7 SoC maintainers' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).