public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-firmware/sof-firmware/
Date: Sun, 18 Oct 2020 15:24:52 +0000 (UTC)	[thread overview]
Message-ID: <1603034679.02b072a6101ef908c4f4a26e862d12e188820f8a.zlogene@gentoo> (raw)

commit:     02b072a6101ef908c4f4a26e862d12e188820f8a
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Sun Oct 18 15:24:39 2020 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Sun Oct 18 15:24:39 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=02b072a6

sys-firmware/sof-firmware: Stabilize 1.5.1 amd64, #749159

Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>

 sys-firmware/sof-firmware/sof-firmware-1.5.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sys-firmware/sof-firmware/sof-firmware-1.5.1.ebuild b/sys-firmware/sof-firmware/sof-firmware-1.5.1.ebuild
index cfd84283ad7..b3ae0343284 100644
--- a/sys-firmware/sof-firmware/sof-firmware-1.5.1.ebuild
+++ b/sys-firmware/sof-firmware/sof-firmware-1.5.1.ebuild
@@ -10,7 +10,7 @@ SRC_URI="https://github.com/thesofproject/sof-bin/archive/stable-v${PV}.tar.gz -
 
 LICENSE="BSD"
 SLOT="0"
-KEYWORDS="~amd64"
+KEYWORDS="amd64"
 IUSE=""
 
 S=${WORKDIR}/sof-bin-stable-v${PV}


             reply	other threads:[~2020-10-18 15:24 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-18 15:24 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-29 19:37 [gentoo-commits] repo/gentoo:master commit in: sys-firmware/sof-firmware/ Sam James
2024-09-29 18:27 Pacho Ramos
2024-07-18 19:03 Pacho Ramos
2024-07-18 19:03 Pacho Ramos
2024-07-08  9:40 Sam James
2024-04-09 15:54 Arthur Zamarin
2024-04-07 16:44 Pacho Ramos
2024-04-07 16:44 Pacho Ramos
2024-03-07 15:03 Pacho Ramos
2024-03-07 15:03 Pacho Ramos
2024-02-05 22:05 Sam James
2024-01-28 17:35 Matt Turner
2023-12-20 10:36 Sam James
2023-12-20 10:04 Pacho Ramos
2023-12-20 10:04 Pacho Ramos
2023-12-20 10:02 Pacho Ramos
2023-11-24 12:18 Arthur Zamarin
2023-11-24 10:58 Pacho Ramos
2023-11-10 16:20 Pacho Ramos
2023-10-01 17:45 Pacho Ramos
2023-10-01 17:45 Pacho Ramos
2023-07-30 12:46 Sam James
2023-07-08 21:44 Sam James
2023-07-08 10:56 Pacho Ramos
2023-07-08 10:56 Pacho Ramos
2023-05-14 16:31 Sam James
2023-05-14 11:37 Pacho Ramos
2023-05-14 11:37 Pacho Ramos
2023-02-23 13:41 Sam James
2023-02-23 13:08 Pacho Ramos
2023-02-23 13:08 Pacho Ramos
2022-12-25 16:42 Sam James
2022-12-25 10:03 Pacho Ramos
2022-12-25 10:03 Pacho Ramos
2022-12-25 10:03 Pacho Ramos
2022-11-04  3:11 Matt Turner
2022-09-09  7:34 Agostino Sarubbo
2022-08-17 16:21 Matt Turner
2022-07-31 11:05 Agostino Sarubbo
2022-07-29 18:08 Matt Turner
2022-04-29  5:58 Sam James
2022-04-29  4:42 Sam James
2022-04-29  4:41 Sam James
2022-01-31 18:50 Sam James
2021-12-22  3:57 Sam James
2021-12-21  3:06 Sam James
2021-10-10 14:20 Andreas K. Hüttel
2021-10-10 14:20 Andreas K. Hüttel
2021-10-10 14:20 Andreas K. Hüttel
2021-05-08 16:03 Matt Turner
2020-07-29  5:38 Matt Turner
2020-04-07  8:40 Andreas K. Hüttel

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=1603034679.02b072a6101ef908c4f4a26e862d12e188820f8a.zlogene@gentoo \
    --to=zlogene@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