From: patchwork-bot+linux-soc@kernel.org
To: Andrew Davis <afd@ti.com>
Cc: soc@kernel.org
Subject: Re: [PATCH] ARM: mach-hpe: Rework support and directory structure
Date: Mon, 15 Sep 2025 13:51:01 +0000 [thread overview]
Message-ID: <175794426123.4179625.15660215322664851936.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250813170308.290349-1-afd@ti.com>
Hello:
This patch was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Wed, 13 Aug 2025 12:03:08 -0500 you wrote:
> Having a platform need a mach-* directory should be seen as a negative,
> it means the platform needs special non-standard handling. ARM64 support
> does not allow mach-* directories at all. While we may not get to that
> given all the non-standard architectures we support, we should still try
> to get as close as we can and reduce the number of mach directories.
>
> The mach-hpe/ directory and files, provides just one "feature":
> having the kernel print the machine name if the DTB does not also contain
> a "model" string (which they always do). To reduce the number of mach-*
> directories let's do without that feature and remove this directory.
>
> [...]
Here is the summary with links:
- ARM: mach-hpe: Rework support and directory structure
https://git.kernel.org/soc/soc/c/9685b2975972
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-09-15 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 17:03 [PATCH] ARM: mach-hpe: Rework support and directory structure Andrew Davis
2025-09-15 13:51 ` patchwork-bot+linux-soc [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-11 20:26 Andrew Davis
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=175794426123.4179625.15660215322664851936.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=afd@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.