All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <florian.fainelli@broadcom.com>
To: soc@kernel.org
Cc: Rosen Penev <rosenp@gmail.com>,
	Florian Fainelli <florian.fainelli@broadcom.com>,
	linux-arm-kernel@lists.infradead.org, arnd@arndb.de,
	khilman@kernel.org, bcm-kernel-feedback-list@broadcom.com
Subject: [GIT PULL v2] Broadcom devicetree fixes for 7.2
Date: Thu, 30 Jul 2026 16:25:19 -0700	[thread overview]
Message-ID: <20260730232519.2706487-1-florian.fainelli@broadcom.com> (raw)

The following changes since commit dc59e4fea9d83f03bad6bddf3fa2e52491777482:

  Linux 7.2-rc1 (2026-06-28 12:01:31 -0700)

are available in the Git repository at:

  https://github.com/Broadcom/stblinux.git tags/arm-soc/for-7.2/devicetree-fixes-v2

for you to fetch changes up to 6de6732c4c784ce64e2457630ca800dfe5efb774:

  ARM: dts: BCM5301X: EA9200: fix NVRAM size (2026-07-29 15:42:57 -0700)

----------------------------------------------------------------
This pull request contains Broadcom ARM-based SoCs Device Tree fixes for
7.2, please pull the following:

- Rosen fixes the Linksys EA9200 NVRAM DT size, the 2nd PCIe controller
  interrupt that was duplicated

----------------------------------------------------------------
Rosen Penev (2):
      ARM: dts: BCM5301X: fix PCIe controller 2 second interrupt
      ARM: dts: BCM5301X: EA9200: fix NVRAM size

 arch/arm/boot/dts/broadcom/bcm-ns.dtsi                | 2 +-
 arch/arm/boot/dts/broadcom/bcm4709-linksys-ea9200.dts | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

             reply	other threads:[~2026-07-30 23:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30 23:25 Florian Fainelli [this message]
2026-08-04 20:20 ` [GIT PULL v2] Broadcom devicetree fixes for 7.2 patchwork-bot+linux-soc
2026-08-04 20:20 ` 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=20260730232519.2706487-1-florian.fainelli@broadcom.com \
    --to=florian.fainelli@broadcom.com \
    --cc=arnd@arndb.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=rosenp@gmail.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.