public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: arm@kernel.org
Cc: soc@kernel.org, linux-rockchip@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL v2] Rockchip dts fixes for 7.0 #1
Date: Mon, 23 Mar 2026 22:58:16 +0100	[thread overview]
Message-ID: <5057236.GXAFRqVoOG@phil> (raw)

Hi SoC maintainers,

As requested by Krzysztof, here is a more condensed PR.

Changes in v2 are that I dropped fixes for dt-schema errors and fixes
for commits introduced not closesly to the current release. These have
been moved to the current branches.

The Pinebook regression fix actually also is for a commit from august
last year, but fixes an actively tracked regression, so maybe carries
a bit more weight.


Please pull

Thanks
Heiko


The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:

  Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v7.0-rockchip-dtsfixes1-v2

for you to fetch changes up to 29d1f56c4f3001b7f547123e0a307c009ac717f8:

  Revert "arm64: dts: rockchip: Further describe the WiFi for the Pinebook Pro" (2026-02-22 23:28:06 +0100)

----------------------------------------------------------------
Revert to fix a regression that breaks Wifi support for a large part
of Pinebook Pro users (multiple Wifi chipsets).

----------------------------------------------------------------
Heiko Stuebner (1):
      Revert "arm64: dts: rockchip: Further describe the WiFi for the Pinebook Pro"

 arch/arm64/boot/dts/rockchip/rk3399-pinebook-pro.dts | 18 ------------------
 1 file changed, 18 deletions(-)





             reply	other threads:[~2026-03-23 21:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23 21:58 Heiko Stuebner [this message]
2026-03-27 11:57 ` [GIT PULL v2] Rockchip dts fixes for 7.0 #1 Krzysztof Kozlowski

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=5057236.GXAFRqVoOG@phil \
    --to=heiko@sntech.de \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --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