From: Chester Lin <clin@suse.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Olof Johansson" <olof@lixom.net>,
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 20:58:54 +0800 [thread overview]
Message-ID: <YpS/jhQf6zLXZSvy@linux-8mug> (raw)
In-Reply-To: <CAK8P3a2A_KHKWN3O2Wcy66yCC+T0eBsK8pNcGuLHN-BVeQ1ymw@mail.gmail.com>
Hi Arnd,
On Mon, May 30, 2022 at 08:58:47AM +0200, Arnd Bergmann wrote:
> 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 ;-)
>
Thanks for your guidance and sorry for any inconvenience this causes. I will
wait for the next cycle.
> - 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
Sure, I will describe more information.
> 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.
>
Sorry for the missing subject line. Will fix it.
> - 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.
>
Thanks for the reminder.
> Please address these and resend.
>
> Arnd
>
WARNING: multiple messages have this Message-ID (diff)
From: Chester Lin <clin@suse.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Olof Johansson" <olof@lixom.net>,
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 20:58:54 +0800 [thread overview]
Message-ID: <YpS/jhQf6zLXZSvy@linux-8mug> (raw)
In-Reply-To: <CAK8P3a2A_KHKWN3O2Wcy66yCC+T0eBsK8pNcGuLHN-BVeQ1ymw@mail.gmail.com>
Hi Arnd,
On Mon, May 30, 2022 at 08:58:47AM +0200, Arnd Bergmann wrote:
> 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 ;-)
>
Thanks for your guidance and sorry for any inconvenience this causes. I will
wait for the next cycle.
> - 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
Sure, I will describe more information.
> 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.
>
Sorry for the missing subject line. Will fix it.
> - 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.
>
Thanks for the reminder.
> Please address these and resend.
>
> Arnd
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-05-30 12:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 6:21 [GIT PULL] arm64: s32g changes for v5.19 Chester Lin
2022-05-30 6:21 ` Chester Lin
2022-05-30 6:58 ` Arnd Bergmann
2022-05-30 6:58 ` Arnd Bergmann
2022-05-30 12:58 ` Chester Lin [this message]
2022-05-30 12:58 ` Chester Lin
2022-05-30 13:26 ` Arnd Bergmann
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=YpS/jhQf6zLXZSvy@linux-8mug \
--to=clin@suse.com \
--cc=afaerber@suse.de \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--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 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.