From: Krzysztof Kozlowski <krzk@kernel.org>
To: Dinh Nguyen <dinguyen@kernel.org>,
linux-arm-kernel@lists.infradead.org, soc@lists.linux.dev
Subject: Re: [GIT PULL] arm64: dts: socfpga: updates for v7.1
Date: Mon, 30 Mar 2026 18:57:59 +0200 [thread overview]
Message-ID: <ab97dc0e-b0b4-420e-9c5b-0a27165ecdc1@kernel.org> (raw)
In-Reply-To: <20260330112844.240664-1-dinguyen@kernel.org>
On 30/03/2026 13:28, Dinh Nguyen wrote:
> The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
>
> Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git tags/socfpga_updates_for_v7.1
>
> for you to fetch changes up to 9d29bcefcdbec4498fe0539e6d8a4e7962d92489:
>
> arm64: dts: intel: agilex5: Drop CPU masks from GICv3 PPI interrupts (2026-03-10 21:10:05 -0500)
>
> ----------------------------------------------------------------
> SoCFPGA DTS updates for v7.1
> - dt-bindings updates:
> - Document fallback compatible for Stratix10 SoCDK eMMC board
> - Document compatible for the Agilex5 SoCFPGA modular board
>
> - Add emmc support for the Stratix10
> - Drop CPU masks from the GICv3 PPI interrupts for Agilex5
>
> ----------------------------------------------------------------
> Dinh Nguyen (1):
> dt-bindings: intel: Add Agilex5 SoCFPGA modular board
Your commit does not end with SoB. Intentional changelog in the patch
commit is fine if it follows standard commit rules, but here it does not
and also --- separator means changelog was not intentional.
Please use b4 to apply patches.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-03-30 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 11:28 [GIT PULL] arm64: dts: socfpga: updates for v7.1 Dinh Nguyen
2026-03-30 16:57 ` Krzysztof Kozlowski [this message]
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=ab97dc0e-b0b4-420e-9c5b-0a27165ecdc1@kernel.org \
--to=krzk@kernel.org \
--cc=dinguyen@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=soc@lists.linux.dev \
/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