From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-kernel/raspberrypi-sources/
Date: Sat, 30 Dec 2023 03:04:57 +0000 (UTC) [thread overview]
Message-ID: <1703905404.4f0799dd3cb80fd121d4ef00db59c59ea5f5d48d.sam@gentoo> (raw)
commit: 4f0799dd3cb80fd121d4ef00db59c59ea5f5d48d
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Dec 30 03:03:24 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Dec 30 03:03:24 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4f0799dd
sys-kernel/raspberrypi-sources: Stabilize 6.1.21_p20230405 arm64, #921010
Signed-off-by: Sam James <sam <AT> gentoo.org>
.../raspberrypi-sources/raspberrypi-sources-6.1.21_p20230405.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sys-kernel/raspberrypi-sources/raspberrypi-sources-6.1.21_p20230405.ebuild b/sys-kernel/raspberrypi-sources/raspberrypi-sources-6.1.21_p20230405.ebuild
index 254fa012aaf1..16912b545378 100644
--- a/sys-kernel/raspberrypi-sources/raspberrypi-sources-6.1.21_p20230405.ebuild
+++ b/sys-kernel/raspberrypi-sources/raspberrypi-sources-6.1.21_p20230405.ebuild
@@ -27,7 +27,7 @@ SRC_URI="
${GENPATCHES_URI}
"
-KEYWORDS="arm ~arm64"
+KEYWORDS="arm arm64"
PATCHES=("${FILESDIR}"/${PN}-6.1.21-gentoo-kconfig.patch)
next reply other threads:[~2023-12-30 3:05 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-30 3:04 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-12 9:44 [gentoo-commits] repo/gentoo:master commit in: sys-kernel/raspberrypi-sources/ Michał Górny
2024-10-12 9:44 Michał Górny
2024-09-03 17:36 Viorel Munteanu
2024-09-03 17:22 Viorel Munteanu
2024-08-23 13:00 Arthur Zamarin
2024-08-13 16:08 Arthur Zamarin
2024-07-12 16:57 Viorel Munteanu
2024-07-12 16:57 Viorel Munteanu
2024-04-20 3:20 Sam James
2023-12-30 3:04 Sam James
2023-06-07 16:39 Sam James
2023-03-24 14:14 Arthur Zamarin
2023-03-10 6:02 Dennis Lamm
2023-03-04 6:04 Arthur Zamarin
2023-03-04 5:47 Arthur Zamarin
2023-02-02 19:54 Dennis Lamm
2023-02-02 19:54 Dennis Lamm
2023-01-05 5:50 Dennis Lamm
2023-01-05 5:50 Dennis Lamm
2023-01-05 5:50 Dennis Lamm
2022-10-28 6:33 Dennis Lamm
2022-04-26 4:47 Dennis Lamm
2022-04-26 4:47 Dennis Lamm
2022-04-09 19:46 Arthur Zamarin
2022-04-09 19:36 Arthur Zamarin
2022-04-06 6:57 Dennis Lamm
2022-04-06 6:57 Dennis Lamm
2022-03-22 1:54 Sam James
2021-12-05 1:29 Sam James
2021-12-05 1:28 Sam James
2021-12-05 1:28 Sam James
2021-09-03 1:53 Sam James
2021-03-22 5:22 Sam James
2021-02-05 18:51 Sam James
2021-02-05 18:51 Sam James
2021-02-05 18:51 Sam James
2021-02-05 18:51 Sam James
2020-12-07 18:05 Sam James
2020-07-28 0:10 Sam James
2019-12-04 23:23 Andrey Utkin
2019-12-04 23:23 Andrey Utkin
2019-12-04 23:23 Andrey Utkin
2019-12-04 23:23 Andrey Utkin
2019-12-04 23:23 Andrey Utkin
2019-01-11 8:29 Georgy Yakovlev
2018-01-04 17:43 Patrice Clement
2017-12-07 23:04 Steve Arnold
2017-12-07 20:38 Steve Arnold
2017-12-03 15:52 Patrice Clement
2017-10-01 5:44 Alexey Shvetsov
2017-07-12 22:36 Alexey Shvetsov
2017-03-07 7:28 Michael Weber
2017-03-07 7:04 Michael Weber
2016-02-11 8:11 Michael Weber
2016-02-11 7:21 Michael Weber
2015-11-28 13:01 Alfredo Tupone
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=1703905404.4f0799dd3cb80fd121d4ef00db59c59ea5f5d48d.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox