From: Frank Li <Frank.li@oss.nxp.com>
To: soc@kernel.org
Cc: Frank.Li@nxp.com, kernel@pengutronix.de, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, stefano.r@variscite.com,
vjardin@free.fr
Subject: Re: [GIT PULL] iMX fixes for 7.2
Date: Mon, 21 Sep 2026 12:04:04 -0500 [thread overview]
Message-ID: <arFjhMrpfJ0OBjUp@SMW015318> (raw)
In-Reply-To: <20260921160016.1139490-1-Frank.Li@oss.nxp.com>
On Mon, Sep 21, 2026 at 12:00:14PM -0400, Frank.Li@oss.nxp.com wrote:
> From: Frank.Li@nxp.com
>
> The following changes since commit cee9395acd8043be0644b25c34bfa86623f2b935:
>
> Linux 7.3-rc1 (2026-08-30 13:34:40 -0700)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/frank.li/linux.git tags/imx-fixes-7.2
Sorry, I mess up version number, it should be 7.3, I will resend pull
request.
Frank
>
> for you to fetch changes up to 7ba5290db6bf365e46fb70bf13dc2a47048165ea:
>
> arm64: dts: imx8mp-var-dart-sonata: Fix Sonata SD I/O supply (2026-09-11 14:50:09 -0400)
>
> ----------------------------------------------------------------
> iMX fixes for 7.2
>
> - Fix incorrect pinmux values for LX2160A.
> - Fix Sonata SD I/O supply to avoid filesystem I/O errors because the kernel
> was disabling LDO5 during late init.
>
> ----------------------------------------------------------------
> Stefano Radaelli (1):
> arm64: dts: imx8mp-var-dart-sonata: Fix Sonata SD I/O supply
>
> Vincent Jardin (3):
> arm64: dts: lx2160a: fix incorrect pinmux
> arm64: dts: lx2160a: fix IIC1 pinmux submask rejected by pinctrl-single
> arm64: dts: lx2160a: fix the iic5 spi3 pinmux offset and value
>
> arch/arm64/boot/dts/freescale/fsl-lx216x.dtsi | 19 +++++++++++++------
> .../boot/dts/freescale/imx8mp-var-dart-sonata.dts | 1 +
> 2 files changed, 14 insertions(+), 6 deletions(-)
>
prev parent reply other threads:[~2026-09-21 17:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 16:00 [GIT PULL] iMX fixes for 7.2 Frank.Li
2026-09-21 17:04 ` Frank Li [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=arFjhMrpfJ0OBjUp@SMW015318 \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=soc@kernel.org \
--cc=stefano.r@variscite.com \
--cc=vjardin@free.fr \
/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