From: Chester Lin <clin@suse.com>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
arm@kernel.org, soc@kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
"Andreas Färber" <afaerber@suse.de>,
"Matthias Brugger" <mbrugger@suse.com>,
s32@nxp.com
Subject: [GIT PULL] arm64: s32g fixes for v5.19
Date: Tue, 7 Jun 2022 21:55:46 +0800 [thread overview]
Message-ID: <Yp9Y4nGrQ2kVKV6S@linux-8mug> (raw)
Hi Arnd, Olof, and ARM SoC maintainers,
Please pull the following two changes for s32g. Thanks.
The following changes since commit f2906aa863381afb0015a9eb7fefad885d4e5a56:
Linux 5.19-rc1 (2022-06-05 17:18:54 -0700)
are available in the Git repository at:
https://github.com/chesterlintw/linux-s32g.git tags/s32g2-fixes-5.19
for you to fetch changes up to 680c0aee97690c3f595e074a5f677599aac5d26b:
MAINTAINERS: add a new reviewer for S32G (2022-06-07 10:26:05 +0800)
----------------------------------------------------------------
S32G2 fixes for 5.19
- MAINTAINERS: Add s32@nxp.com as a review group.
- dts: Pass unit name to soc node to fix a W=1 build warning.
----------------------------------------------------------------
Chester Lin (1):
MAINTAINERS: add a new reviewer for S32G
Fabio Estevam (1):
arm64: s32g2: Pass unit name to soc node
MAINTAINERS | 1 +
arch/arm64/boot/dts/freescale/s32g2.dtsi | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
WARNING: multiple messages have this Message-ID (diff)
From: Chester Lin <clin@suse.com>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
arm@kernel.org, soc@kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
"Andreas Färber" <afaerber@suse.de>,
"Matthias Brugger" <mbrugger@suse.com>,
s32@nxp.com
Subject: [GIT PULL] arm64: s32g fixes for v5.19
Date: Tue, 7 Jun 2022 21:55:46 +0800 [thread overview]
Message-ID: <Yp9Y4nGrQ2kVKV6S@linux-8mug> (raw)
Hi Arnd, Olof, and ARM SoC maintainers,
Please pull the following two changes for s32g. Thanks.
The following changes since commit f2906aa863381afb0015a9eb7fefad885d4e5a56:
Linux 5.19-rc1 (2022-06-05 17:18:54 -0700)
are available in the Git repository at:
https://github.com/chesterlintw/linux-s32g.git tags/s32g2-fixes-5.19
for you to fetch changes up to 680c0aee97690c3f595e074a5f677599aac5d26b:
MAINTAINERS: add a new reviewer for S32G (2022-06-07 10:26:05 +0800)
----------------------------------------------------------------
S32G2 fixes for 5.19
- MAINTAINERS: Add s32@nxp.com as a review group.
- dts: Pass unit name to soc node to fix a W=1 build warning.
----------------------------------------------------------------
Chester Lin (1):
MAINTAINERS: add a new reviewer for S32G
Fabio Estevam (1):
arm64: s32g2: Pass unit name to soc node
MAINTAINERS | 1 +
arch/arm64/boot/dts/freescale/s32g2.dtsi | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-06-07 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 13:55 Chester Lin [this message]
2022-06-07 13:55 ` [GIT PULL] arm64: s32g fixes for v5.19 Chester Lin
2022-06-14 20:33 ` patchwork-bot+linux-soc
2022-06-14 20:37 ` patchwork-bot+linux-soc
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=Yp9Y4nGrQ2kVKV6S@linux-8mug \
--to=clin@suse.com \
--cc=afaerber@suse.de \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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.