From: Arnd Bergmann <arnd@arndb.de>
To: Chester Lin <clin@suse.com>
Cc: "Olof Johansson" <olof@lixom.net>,
"Arnd Bergmann" <arnd@arndb.de>,
arm@kernel.org, soc@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, "Andreas Färber" <afaerber@suse.de>,
"Matthias Brugger" <mbrugger@suse.com>,
s32@nxp.com, "Fabio Estevam" <festevam@gmail.com>
Subject: Re: [GIT PULL] arm64: s32g changes for v5.19
Date: Mon, 30 May 2022 08:58:47 +0200 [thread overview]
Message-ID: <CAK8P3a2A_KHKWN3O2Wcy66yCC+T0eBsK8pNcGuLHN-BVeQ1ymw@mail.gmail.com> (raw)
In-Reply-To: <YpRiZpZU3kH2xprC@linux-8mug>
On Mon, May 30, 2022 at 8:21 AM Chester Lin <clin@suse.com> wrote:
>
> ----------------------------------------------------------------
> s32g changes for v5.19
>
> ----------------------------------------------------------------
> Chester Lin (1):
> MAINTAINERS: add a new reviewer for S32G
>
> Fabio Estevam (1):
> Pass unit name to soc node to fix the following W=1 build warning:
The patches look fine, but there are a few minor problems with the
submission:
- The branch is based on top of a random commit from the mainline repository,
you should instead always base this on top of an -rc tag in order to not
clutter up the git history or make bisection unnecessarily hard. My 'arm/late'
branch is currently based on a random commit 16477cdfefdb ("Merge tag
'asm-generic-5.19' of
git://git.kernel.org/pub/scm/linux/kernel/git/arnd/asm-generic")
as well, but this is an exception and I will explain it when I send the pull
request ;-)
- The tag description is only a single line, there should be at least some
content in here. Please have a look at other merge commits to see what
you can put in here. For a small number of independent patches like
these two, you can also just forward them to soc@kernel.org as
individual emails without a tag.
- The subject lines of the individual emails should have the right namespace
listed in them, e.g. 'arm64: s32g: ...'. Fabio's patch originally had
this, but it looks like the entire subject line got lost.
- The subject for the pull request indicates that this is meant as your normal
submission, but this is the wrong time for that, because the merge window
is currently open. At this point, only bugfixes get merged, but I do classify
MAINTAINERS changes as bugfixes, so this is actually ok, just change the
subject.
Please address these and resend.
Arnd
next prev parent reply other threads:[~2022-05-30 6:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 6:21 Chester Lin
2022-05-30 6:58 ` Arnd Bergmann [this message]
2022-05-30 12:58 ` Chester Lin
2022-05-30 13: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=CAK8P3a2A_KHKWN3O2Wcy66yCC+T0eBsK8pNcGuLHN-BVeQ1ymw@mail.gmail.com \
--to=arnd@arndb.de \
--cc=afaerber@suse.de \
--cc=arm@kernel.org \
--cc=clin@suse.com \
--cc=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbrugger@suse.com \
--cc=olof@lixom.net \
--cc=s32@nxp.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
all inboxes | Powered by JetHome®