From: Lee Jones <lee.jones@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Michael Walle <michael@walle.cc>, SoC Team <soc@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Olof Johansson <olof@lixom.net>
Subject: Re: [PATCH] MAINTAINERS: add myself as a maintainer for the sl28cpld
Date: Tue, 15 Feb 2022 09:22:50 +0000 [thread overview]
Message-ID: <Ygtw6hJFfDC6fd07@google.com> (raw)
In-Reply-To: <CAK8P3a1aqcsD-fGBgAmsi0qf9Td_y3Ry+o32Z1fU8H3qmEn0GA@mail.gmail.com>
On Mon, 14 Feb 2022, Arnd Bergmann wrote:
> On Mon, Feb 14, 2022 at 5:36 PM Lee Jones <lee.jones@linaro.org> wrote:
> > On Mon, 14 Feb 2022, Arnd Bergmann wrote:
> > > On Mon, Feb 14, 2022 at 3:16 PM Lee Jones <lee.jones@linaro.org> wrote:
> > > >
> > > > Hold on, you're not going to get many Acks if you don't send it to the
> > > > other subsystem maintainers. :)
> > >
> > > I've already applied this one through the soc tree.
> >
> > You did? I missed the acceptance email.
>
> I see now that the automated mails only get sent the submitter and
> the list that is owned by patchwork. I completely missed how this
> was sent to multiple maintainers and just grabbed it from patchwork
> along with some other maintainer changes I picked up.
>
> > It would have been nice to give the other maintainers a chance to look
> > at it first, but I guess it's not a big deal in the great scheme.
>
> Right, I need to find a better process to look at the actual emails
> when going through patchwork. Sorry about that.
No problem at all. Thank you for the explanation.
--
Lee Jones [李琼斯]
Principal Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2022-02-15 9:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 18:46 [PATCH] MAINTAINERS: add myself as a maintainer for the sl28cpld Michael Walle
2022-02-08 9:12 ` patchwork-bot+linux-soc
2022-02-14 14:15 ` Lee Jones
2022-02-14 14:16 ` Lee Jones
2022-02-14 16:22 ` Arnd Bergmann
2022-02-14 16:36 ` Lee Jones
2022-02-14 19:13 ` Arnd Bergmann
2022-02-15 9:22 ` Lee Jones [this message]
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=Ygtw6hJFfDC6fd07@google.com \
--to=lee.jones@linaro.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--cc=olof@lixom.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.