public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Wei Xu <xuwei5@hisilicon.com>
To: <soc@kernel.org>, <arm@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
	Arnd Bergmann <arnd@arndb.de>, <xuwei5@hisilicon.com>,
	<zhangyi.ac@huawei.com>,
	"Wuliebao (Joab, Turing Solution)" <wuliebao@huawei.com>,
	"Shenqingchun(DanielShen)" <daniel.shen@huawei.com>,
	<huangdaode@huawei.com>, <liguozhu@hisilicon.com>,
	"Zengtao (B)" <prime.zeng@hisilicon.com>,
	Jonathan Cameron <Jonathan.Cameron@Huawei.com>,
	<shiju.jose@huawei.com>, <salil.mehta@huawei.com>,
	Shawn Guo <shawnguo@kernel.org>
Subject: [GIT,PULL] arm64: dts: hisilicon: fixes for v7.0
Date: Fri, 27 Mar 2026 15:23:46 +0800	[thread overview]
Message-ID: <69C63082.1000806@hisilicon.com> (raw)

Hi ARM SoC maintainers,

Please consider to pull the following changes.
Thanks!

Best Regards,
Wei

---

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://github.com/hisilicon/linux-hisi.git tags/hisi-dts-fixes-for-7.0

for you to fetch changes up to 1af997cad473d505248df6d9577183bb91f69670:

  arm64: dts: hisilicon: hi3798cv200: Add missing dma-ranges (2026-03-21 03:38:11 +0000)

----------------------------------------------------------------
HiSilicon dts fixes for v7.0

- Correct the PCIe reset GPIO polarity for hi3798cv200-poplar
- Add the missing dma-ranges for hi3798cv200

----------------------------------------------------------------
Shawn Guo (2):
      arm64: dts: hisilicon: poplar: Correct PCIe reset GPIO polarity
      arm64: dts: hisilicon: hi3798cv200: Add missing dma-ranges

 arch/arm64/boot/dts/hisilicon/hi3798cv200-poplar.dts | 2 +-
 arch/arm64/boot/dts/hisilicon/hi3798cv200.dtsi       | 1 +
 2 files changed, 2 insertions(+), 1 deletion(-)


                 reply	other threads:[~2026-03-27  7:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=69C63082.1000806@hisilicon.com \
    --to=xuwei5@hisilicon.com \
    --cc=Jonathan.Cameron@Huawei.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=daniel.shen@huawei.com \
    --cc=huangdaode@huawei.com \
    --cc=liguozhu@hisilicon.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=prime.zeng@hisilicon.com \
    --cc=salil.mehta@huawei.com \
    --cc=shawnguo@kernel.org \
    --cc=shiju.jose@huawei.com \
    --cc=soc@kernel.org \
    --cc=wuliebao@huawei.com \
    --cc=zhangyi.ac@huawei.com \
    /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