Github messages for voidlinux
 help / color / mirror / Atom feed
From: CameronNemo <>
Subject: Re: [PR REVIEW] Pinebook Pro U-Boot: use newer ARM Trusted Firmware
Date: Fri, 11 Sep 2020 21:37:47 +0200	[thread overview]
Message-ID: <20200911193747.-kZPUFd2m2RoUwPdOKp293DWLzunrSFX9ibAnIelRqw@z> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 736 bytes --]

New review comment by CameronNemo on void-packages repository

We could but it would still mean tying versions of one platform to the other platforms. It is a question of whether the distribution wants to update all of the TF-A binaries at the same time (and presumably all of the u-boot binaries as well, otherwise why bother?), or whether the builds should be kept separate and updated independently.

I lean toward the latter because I do not have access to all of the hardware platforms that might be affected by a new release of TF-A. I would feel uncomfortable updating TF-A if I knew I might be breaking something and had no way to verify.

  parent reply	other threads:[~2020-09-11 19:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21  9:57 [PR PATCH] " CameronNemo
2020-09-07  6:10 ` [PR PATCH] [Updated] " CameronNemo
2020-09-11 15:55 ` [PR REVIEW] " sgn
2020-09-11 19:36 ` CameronNemo
2020-09-11 19:37 ` CameronNemo [this message]
2020-10-06  3:43 ` [PR PATCH] [Updated] " CameronNemo
2020-10-06  3:58 ` [PR REVIEW] " CameronNemo
2020-10-06  4:00 ` CameronNemo
2020-10-06 10:30 ` [PR REVIEW] Pinebook Pro U-Boot: update to 2020.10, TF-A 2.3 pullmoll
2020-10-27  3:05 ` [PR PATCH] [Updated] " CameronNemo
2020-11-21 23:43 ` CameronNemo
2020-11-22 19:42 ` CameronNemo
2021-02-16  5:46 ` ericonr
2021-02-16  7:15 ` CameronNemo
2021-02-16  7:16 ` CameronNemo
2021-03-14 20:04 ` Johnnynator
2021-03-15 18:41 ` [PR PATCH] [Closed]: " Johnnynator

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200911193747.-kZPUFd2m2RoUwPdOKp293DWLzunrSFX9ibAnIelRqw@z \ \ \

* 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).