From: Krzysztof Kozlowski <krzk@kernel.org>
To: Gregory CLEMENT <gregory.clement@bootlin.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
arm@kernel.org, soc@kernel.org, Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] ARM: mvebu: fixes for v7.0 (#1)
Date: Sat, 14 Mar 2026 12:17:06 +0100 [thread overview]
Message-ID: <20260314-illustrious-origami-pronghorn-964508@quoll> (raw)
In-Reply-To: <87sea3680w.fsf@BLaptop.bootlin.com>
On Fri, Mar 13, 2026 at 04:53:03PM +0100, Gregory CLEMENT wrote:
> Hi,
>
> Here is the first pull request for fixes for mvebu for v7.0.
>
> Gregory
>
> 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/gclement/mvebu.git tags/mvebu-fixes-7.0-1
>
> for you to fetch changes up to edb7efa767da8bb82d724b85178be251ec4e060e:
>
> dt-bindings: arm64: add Marvell 7k COMe boards (2026-03-13 16:41:11 +0100)
>
> ----------------------------------------------------------------
> mvebu fixes for 7.0 (part 1)
>
> - Add bindings to validate the device tree that has already been merged.
Merged when? Why is this a fix not a development (e.g. documenting
something 10 years old)?
Please write informative pull requests. You want to here provide the
context WHY maintainer should take this as fixes.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-14 11:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 15:53 [GIT PULL] ARM: mvebu: fixes for v7.0 (#1) Gregory CLEMENT
2026-03-14 11:17 ` Krzysztof Kozlowski [this message]
2026-03-16 9:12 ` Gregory CLEMENT
2026-03-14 11:19 ` Krzysztof Kozlowski
-- strict thread matches above, loose matches on Subject: below --
2026-04-09 8:28 Gregory CLEMENT
2026-04-11 8:54 ` 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=20260314-illustrious-origami-pronghorn-964508@quoll \
--to=krzk@kernel.org \
--cc=andrew@lunn.ch \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=gregory.clement@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=sebastian.hesselbarth@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox