From: Vagrant Cascadian <vagrant@debian.org>
To: guix-devel <guix-devel@gnu.org>
Subject: Applying patches to linux-libre-X.Y-source conditionally by architecture
Date: Wed, 12 May 2021 13:46:06 -0700 [thread overview]
Message-ID: <87im3nr88h.fsf@yucca> (raw)
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
When patching linux-libre-X.Y-source, is it possible to apply patches
per-architecture? I ask, because I'd like to apply an aarch64/arm64
patch, but would hate to trigger linux-libre rebuilds for all
architectures just to add trivial patches that would have no affect in
most architectures...
I've done basically this same patch for linux-libre@5.11 and @5.10, and
it would be nice to apply for @5.12, too. If we can't get architecture
specific conditionals, then it would be ideal to apply it at the same
time as the next version bump so as not to rebuild twice on all
architectures.
diff --git a/gnu/packages/linux.scm b/gnu/packages/linux.scm
index a155c29f8b..ac70bdf4f0 100644
--- a/gnu/packages/linux.scm
+++ b/gnu/packages/linux.scm
@@ -489,7 +489,9 @@ corresponding UPSTREAM-SOURCE (an origin), using the given DEBLOB-SCRIPTS."
(define-public linux-libre-5.10-source
(source-with-patches linux-libre-5.10-pristine-source
(list %boot-logo-patch
- %linux-libre-arm-export-__sync_icache_dcache-patch)))
+ %linux-libre-arm-export-__sync_icache_dcache-patch
+ (search-patch
+ "linux-libre-arm64-generic-pinebook-lcd.patch"))))
Thanks!
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next reply other threads:[~2021-05-12 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 20:46 Vagrant Cascadian [this message]
2021-05-30 5:51 ` Applying patches to linux-libre-X.Y-source conditionally by architecture 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=87im3nr88h.fsf@yucca \
--to=vagrant@debian.org \
--cc=guix-devel@gnu.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).