From: Shawn Guo <shawnguo2@yeah.net>
To: soc@kernel.org, arm@kernel.org
Cc: Shawn Guo <shawnguo@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
Stefan Agner <stefan@agner.ch>, Li Yang <leoyang.li@nxp.com>,
kernel@pengutronix.de, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 5/5] i.MX defconfig for 6.9
Date: Mon, 26 Feb 2024 11:41:46 +0800 [thread overview]
Message-ID: <20240226034147.233993-5-shawnguo2@yeah.net> (raw)
In-Reply-To: <20240226034147.233993-1-shawnguo2@yeah.net>
From: Shawn Guo <shawnguo@kernel.org>
The following changes since commit 6613476e225e090cc9aad49be7fa504e290dd33d:
Linux 6.8-rc1 (2024-01-21 14:11:32 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-defconfig-6.9
for you to fetch changes up to f1a9ff95971a879572f56bbc8b1e1ca0b1a812b8:
arm64: defconfig: enable i.MX8MP ldb bridge (2024-02-06 18:34:58 +0800)
----------------------------------------------------------------
i.MX defconfig for 6.9:
- Enable VF610 GPIO driver for both arm64 and i.MX ARM defconfig.
- Enable i.MX8MP LDB bridge and i.MX8QXP support drivers in arm64
defconfig.
----------------------------------------------------------------
Alexander Stein (1):
arm64: defconfig: Enable i.MX8QXP device drivers
Martin Kaiser (2):
ARM: imx_v6_v7_defconfig: enable the vf610 gpio driver
arm64: defconfig: enable the vf610 gpio driver
Yannic Moog (1):
arm64: defconfig: enable i.MX8MP ldb bridge
arch/arm/configs/imx_v6_v7_defconfig | 1 +
arch/arm64/configs/defconfig | 8 ++++++++
2 files changed, 9 insertions(+)
prev parent reply other threads:[~2024-02-26 3:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 3:41 [GIT PULL 1/5] i.MX SoC changes for 6.9 Shawn Guo
2024-02-26 3:41 ` [GIT PULL 2/5] i.MX dt-bindings " Shawn Guo
2024-02-26 3:41 ` [GIT PULL 3/5] i.MX ARM device tree " Shawn Guo
2024-02-26 3:41 ` [GIT PULL 4/5] i.MX arm64 " Shawn Guo
2024-02-26 3:41 ` Shawn Guo [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=20240226034147.233993-5-shawnguo2@yeah.net \
--to=shawnguo2@yeah.net \
--cc=arm@kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=shawnguo@kernel.org \
--cc=soc@kernel.org \
--cc=stefan@agner.ch \
/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