Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <florian.fainelli@broadcom.com>
To: soc@kernel.org
Cc: Martin Wetterwald <martin@wetterwald.eu>,
	Jai Luthra <jai.luthra@ideasonboard.com>,
	Gaston Gonzalez # Raspberry Pi Zero <gascoar@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 1/2] Broadcom drivers fixes for 7.4
Date: Fri, 13 Nov 2026 19:45:49 -0800	[thread overview]
Message-ID: <20261114034550.878760-1-florian.fainelli@broadcom.com> (raw)

The following changes since commit 7475ea8b58616b33c04afb976cf0fbaad9dd63fb:

  Linux 7.4-rc2 (2026-11-08 16:22:20 -0800)

are available in the Git repository at:

  https://github.com/Broadcom/stblinux.git tags/arm-soc/for-7.4/drivers-fixes

for you to fetch changes up to 109d5fda6c07649d4bb9270fd99f5c75e3e49fde:

  platform/raspberrypi: vchiq: register bus at subsys_initcall (2026-11-13 19:36:46 -0800)

----------------------------------------------------------------
This pull request contains Broadcom SoCs drivers for 7.4, please pull
the following:

- Martin fixes the vchiq driver probing order to restore audio via
  bcm2835-audio on Raspberry Pi platforms

----------------------------------------------------------------
Martin Wetterwald (1):
      platform/raspberrypi: vchiq: register bus at subsys_initcall

 drivers/platform/raspberrypi/vchiq-interface/vchiq_arm.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


             reply	other threads:[~2026-11-14  3:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-14  3:45 Florian Fainelli [this message]
2026-11-14  3:45 ` [GIT PULL 2/2] Broadcom maintainers fixes for 7.4 Florian Fainelli

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=20261114034550.878760-1-florian.fainelli@broadcom.com \
    --to=florian.fainelli@broadcom.com \
    --cc=arnd@arndb.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=gascoar@gmail.com \
    --cc=jai.luthra@ideasonboard.com \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=martin@wetterwald.eu \
    --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