All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: soc@kernel.org, arm@kernel.org
Cc: Fabio Estevam <festevam@gmail.com>,
	Stefan Agner <stefan@agner.ch>, Li Yang <leoyang.li@nxp.com>,
	kernel@pengutronix.de, linux-imx@nxp.com,
	linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] i.MX fixes for 5.11, round 3
Date: Tue, 2 Feb 2021 15:14:42 +0800	[thread overview]
Message-ID: <20210202071441.GP907@dragon> (raw)

The following changes since commit 82c082784e03a9a9c043345f9bc04bc8254cf6da:

  firmware: imx: select SOC_BUS to fix firmware build (2021-01-18 15:49:07 +0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-fixes-5.11-3

for you to fetch changes up to aa880c6f3ee6dbd0d5ab02026a514ff8ea0a3328:

  arm64: dts: ls1046a: fix dcfg address range (2021-01-30 21:28:23 +0800)

----------------------------------------------------------------
i.MX fixes for 5.11, round 3:

- Fix DCFG address range on LS1046A SoC.

----------------------------------------------------------------
Zyta Szpak (1):
      arm64: dts: ls1046a: fix dcfg address range

 arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: soc@kernel.org, arm@kernel.org
Cc: Stefan Agner <stefan@agner.ch>, Li Yang <leoyang.li@nxp.com>,
	linux-imx@nxp.com, kernel@pengutronix.de,
	Fabio Estevam <festevam@gmail.com>,
	linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] i.MX fixes for 5.11, round 3
Date: Tue, 2 Feb 2021 15:14:42 +0800	[thread overview]
Message-ID: <20210202071441.GP907@dragon> (raw)
Message-ID: <20210202071442.rAFWdjquIxL9vf62qMKrDm80kZ0jRMhStNouLxdzboQ@z> (raw)

The following changes since commit 82c082784e03a9a9c043345f9bc04bc8254cf6da:

  firmware: imx: select SOC_BUS to fix firmware build (2021-01-18 15:49:07 +0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-fixes-5.11-3

for you to fetch changes up to aa880c6f3ee6dbd0d5ab02026a514ff8ea0a3328:

  arm64: dts: ls1046a: fix dcfg address range (2021-01-30 21:28:23 +0800)

----------------------------------------------------------------
i.MX fixes for 5.11, round 3:

- Fix DCFG address range on LS1046A SoC.

----------------------------------------------------------------
Zyta Szpak (1):
      arm64: dts: ls1046a: fix dcfg address range

 arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi | 2 +-
 1 file changed, 1 insertion(+), 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:[~2021-02-02  7:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-02  7:14 Shawn Guo [this message]
2021-02-02  7:14 ` [GIT PULL] i.MX fixes for 5.11, round 3 Shawn Guo
2021-02-02 16:47 ` Arnd Bergmann
2021-02-02 16:47   ` 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=20210202071441.GP907@dragon \
    --to=shawnguo@kernel.org \
    --cc=arm@kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=leoyang.li@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --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 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.