From: Thomas Monjalon <thomas@monjalon.net>
To: Wathsala Vithanage <wathsala.vithanage@arm.com>,
Dhruv Tripathi <dhruv.tripathi@arm.com>,
Doug Foster <doug.foster@arm.com>
Cc: dev@dpdk.org, nd@arm.com
Subject: Re: [PATCH] doc/linux_gsg: add build instructions for new Arm SoCs
Date: Sun, 20 Jul 2025 21:54:23 +0200 [thread overview]
Message-ID: <4444415.ejJDZkT8p0@thomas> (raw)
In-Reply-To: <20250516185307.1494231-1-doug.foster@arm.com>
16/05/2025 20:53, Doug Foster:
> Add explanation of recent build configuration changes for Arm SoCs and
> instructions for adding a build configuration for a new Arm SoC.
>
> Signed-off-by: Doug Foster <doug.foster@arm.com>
> Reviewed-by: Wathsala Vithanage <wathsala.vithanage@arm.com>
> Reviewed-by: Dhruv Tripathi <dhruv.tripathi@arm.com>
Reworded a little to make simpler and avoid the word "recent" in a permanent guide.
Applied, thanks.
prev parent reply other threads:[~2025-07-20 19:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 18:53 Doug Foster
2025-07-20 19:54 ` Thomas Monjalon [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=4444415.ejJDZkT8p0@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=dhruv.tripathi@arm.com \
--cc=doug.foster@arm.com \
--cc=nd@arm.com \
--cc=wathsala.vithanage@arm.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;
as well as URLs for NNTP newsgroup(s).