public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Chester Lin <clin@suse.com>
To: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
	arm@kernel.org, soc@kernel.org
Cc: 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: [GIT PULL] arm64: s32g changes for v5.19
Date: Mon, 30 May 2022 14:21:26 +0800	[thread overview]
Message-ID: <YpRiZpZU3kH2xprC@linux-8mug> (raw)

Hi Arnd, Olof, and ARM SoC maintainers,

Please pull the following two changes for s32g. Thanks.

The following changes since commit b00ed48bb0a7c295facf9036135a573a5cdbe7de:

  Merge tag 'dmaengine-5.19-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine (2022-05-29 11:38:27 -0700)

are available in the Git repository at:

  https://github.com/chesterlintw/linux-s32g.git tags/s32g2-5.19

for you to fetch changes up to fdb31e581566f7a2790b602f62701fce96b16443:

  MAINTAINERS: add a new reviewer for S32G (2022-05-30 11:21:49 +0800)

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

 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

             reply	other threads:[~2022-05-30  6:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30  6:21 Chester Lin [this message]
2022-05-30  6:58 ` [GIT PULL] arm64: s32g changes for v5.19 Arnd Bergmann
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=YpRiZpZU3kH2xprC@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox