From: Herman Rimm via Guix-patches via <guix-patches@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: 74849@debbugs.gnu.org
Subject: [bug#74849] [PATCH v2 2/6] gnu: arm-trusted-firmware: Reformat.
Date: Fri, 20 Dec 2024 21:11:08 +0100 [thread overview]
Message-ID: <5bqv7yz2ywd3bujymxxyexsbctm6lt7phx7jnse4dy2jf5m22r@2ezmdjdzgjwu> (raw)
In-Reply-To: <87o717uu0w.fsf@contorta>
Hi,
On Thu, Dec 19, 2024 at 03:34:23PM -0800, Vagrant Cascadian wrote:
> What is this referring to? What modules that were not used before?
It is referring to the modules field of the origin record.
> What I do not see mentioned is that it reworks how "native-build?" is
> used a bit. Could that be split in a separate patch?
I'll submit whitespace changes separately in future patch series.
Regarding the (i.MX 8MQ) ATF patches, I seem to need a GitHub account to
submit them upstream, per [1]. I don't agree to the registration terms.
Cheers,
Herman
[1]: https://trustedfirmware-a.readthedocs.io/en/latest/process/contributing.html
next prev parent reply other threads:[~2024-12-20 20:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 12:23 [bug#74849] [PATCH 0/6] Update ARM Trusted Firmware Herman Rimm via Guix-patches via
2024-12-13 12:25 ` [bug#74849] [PATCH 1/6] gnu: arm-trusted-firmware-rk3399: Reformat Herman Rimm via Guix-patches via
2024-12-13 12:25 ` [bug#74849] [PATCH 2/6] gnu: arm-trusted-firmware: Reformat Herman Rimm via Guix-patches via
2024-12-13 12:25 ` [bug#74849] [PATCH 3/6] import: utils: Move guix-name to (guix utils) Herman Rimm via Guix-patches via
2024-12-17 13:52 ` Ludovic Courtès
2024-12-13 12:25 ` [bug#74849] [PATCH 4/6] gnu: make-arm-trusted-firmware: Use guix-name Herman Rimm via Guix-patches via
2024-12-15 8:04 ` Vagrant Cascadian
2024-12-15 23:05 ` Herman Rimm via Guix-patches via
2024-12-19 19:50 ` [bug#74849] fixed guix-name missing, but still fails on aarch64 Vagrant Cascadian
2024-12-13 12:25 ` [bug#74849] [PATCH 5/6] gnu: make-arm-trusted-firmware: Update to 2.12 Herman Rimm via Guix-patches via
2024-12-13 12:25 ` [bug#74849] [PATCH 6/6] gnu: arm-trusted-firmware-imx8mq: Fix build Herman Rimm via Guix-patches via
2024-12-15 8:36 ` [bug#74849] [PATCH 0/6] Update ARM Trusted Firmware Vagrant Cascadian
2024-12-19 22:10 ` [bug#74849] [PATCH v2 " Herman Rimm via Guix-patches via
2024-12-19 22:10 ` [bug#74849] [PATCH v2 1/6] gnu: arm-trusted-firmware-rk3399: Reformat Herman Rimm via Guix-patches via
2024-12-19 22:10 ` [bug#74849] [PATCH v2 2/6] gnu: arm-trusted-firmware: Reformat Herman Rimm via Guix-patches via
2024-12-19 23:34 ` Vagrant Cascadian
2024-12-20 20:11 ` Herman Rimm via Guix-patches via [this message]
2024-12-19 22:10 ` [bug#74849] [PATCH v2 3/6] import: utils: Move guix-name to (guix utils) Herman Rimm via Guix-patches via
[not found] ` <87cyhmmrot.fsf@nicolasgoaziou.fr>
2024-12-20 17:50 ` Herman Rimm via Guix-patches via
2024-12-19 22:10 ` [bug#74849] [PATCH v2 4/6] gnu: make-arm-trusted-firmware: Use guix-name Herman Rimm via Guix-patches via
2024-12-19 22:10 ` [bug#74849] [PATCH v2 5/6] gnu: make-arm-trusted-firmware: Update to 2.12 Herman Rimm via Guix-patches via
2024-12-19 22:10 ` [bug#74849] [PATCH v2 6/6] gnu: arm-trusted-firmware-imx8mq: Fix build Herman Rimm via Guix-patches via
2024-12-19 23:18 ` [bug#74849] [PATCH v2 0/6] Update ARM Trusted Firmware Vagrant Cascadian
2024-12-20 0:22 ` bug#74849: " Vagrant Cascadian
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5bqv7yz2ywd3bujymxxyexsbctm6lt7phx7jnse4dy2jf5m22r@2ezmdjdzgjwu \
--to=guix-patches@gnu.org \
--cc=74849@debbugs.gnu.org \
--cc=herman@rimm.ee \
--cc=vagrant@debian.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).