public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "WANG Xuerui" <xen0n@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-libs/libnvme/
Date: Thu, 19 May 2022 11:24:51 +0000 (UTC)	[thread overview]
Message-ID: <1652959467.cf2693904325131c795180a4ad9e79fa19444521.xen0n@gentoo> (raw)

commit:     cf2693904325131c795180a4ad9e79fa19444521
Author:     WANG Xuerui <xen0n <AT> gentoo <DOT> org>
AuthorDate: Thu May 19 11:24:27 2022 +0000
Commit:     WANG Xuerui <xen0n <AT> gentoo <DOT> org>
CommitDate: Thu May 19 11:24:27 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cf269390

sys-libs/libnvme: keyword 1.0 for ~loong

Signed-off-by: WANG Xuerui <xen0n <AT> gentoo.org>

 sys-libs/libnvme/libnvme-1.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sys-libs/libnvme/libnvme-1.0.ebuild b/sys-libs/libnvme/libnvme-1.0.ebuild
index 2a0a33ef7701..2894e4e7f447 100644
--- a/sys-libs/libnvme/libnvme-1.0.ebuild
+++ b/sys-libs/libnvme/libnvme-1.0.ebuild
@@ -12,7 +12,7 @@ SLOT="0"
 IUSE="+json ssl +uuid"
 
 SRC_URI="https://github.com/linux-nvme/libnvme/archive/refs/tags/v${PV}.tar.gz -> ${P}.tar.gz"
-KEYWORDS="~amd64 ~arm64 ~ppc64 ~riscv ~x86"
+KEYWORDS="~amd64 ~arm64 ~loong ~ppc64 ~riscv ~x86"
 DEPEND="
 	json? ( dev-libs/json-c:= )
 	ssl? ( >=dev-libs/openssl-1.1:= )


             reply	other threads:[~2022-05-19 11:24 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-19 11:24 WANG Xuerui [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-18  0:49 [gentoo-commits] repo/gentoo:master commit in: sys-libs/libnvme/ Patrick McLean
2025-03-09 22:22 Sam James
2024-12-14 17:17 Arthur Zamarin
2024-12-12 19:31 Arthur Zamarin
2024-12-12 19:31 Arthur Zamarin
2024-12-12 12:44 Arthur Zamarin
2024-12-12 12:44 Arthur Zamarin
2024-12-12 11:17 Sam James
2024-12-12 11:09 Sam James
2024-11-16  0:57 Patrick McLean
2024-10-31 20:37 Patrick McLean
2024-10-31 20:37 Patrick McLean
2024-09-23  8:18 Arthur Zamarin
2024-09-23  7:13 Arthur Zamarin
2024-09-23  0:32 Sam James
2024-08-05 18:50 Patrick McLean
2024-06-25  2:39 Sam James
2024-06-25  2:39 Sam James
2024-05-16 14:58 Arthur Zamarin
2024-05-03 21:57 Patrick McLean
2024-03-24 11:35 Sam James
2024-03-24 11:29 Sam James
2024-02-14 18:30 Patrick McLean
2024-02-06  5:36 Sam James
2024-02-06  3:05 Sam James
2024-02-06  2:56 Sam James
2024-02-03  6:56 Sam James
2024-02-02 17:51 Arthur Zamarin
2024-02-02 13:34 Arthur Zamarin
2024-02-02 12:38 Arthur Zamarin
2024-02-02  5:13 Sam James
2023-12-21  0:07 Ionen Wolkens
2023-12-20 11:08 Sam James
2023-12-10  1:38 Ionen Wolkens
2023-12-09  7:54 Arthur Zamarin
2023-11-24  9:31 Sam James
2023-11-08  5:35 Sam James
2023-11-08  5:35 Sam James
2023-11-08  1:50 Sam James
2023-11-08  1:50 Sam James
2023-11-08  1:50 Sam James
2023-11-04 10:52 Sam James
2023-11-02 14:41 Joonas Niilola
2023-10-26 13:04 Sam James
2023-09-29  7:05 Patrick McLean
2023-09-13  5:38 Sam James
2023-08-19 15:37 Arthur Zamarin
2023-08-19  9:24 Sam James
2023-08-19  6:23 Sam James
2023-07-09  4:39 Sam James
2023-07-09  4:37 Sam James
2023-07-09  2:13 Sam James
2023-06-30 23:14 Patrick McLean
2023-05-29 20:18 Sam James
2023-05-27 10:57 Arthur Zamarin
2023-05-23 15:16 Arthur Zamarin
2023-05-23 15:16 Arthur Zamarin
2023-04-07  5:07 Sam James
2023-04-07  5:07 Sam James
2023-04-07  5:07 Sam James
2023-04-07  5:07 Sam James
2023-03-31 19:13 Patrick McLean
2023-01-31 23:06 Patrick McLean
2022-12-26  8:35 Sam James
2022-12-25 22:06 David Seifert
2022-11-25  6:02 Sam James
2022-11-25  5:16 Sam James
2022-11-25  5:16 Sam James
2022-11-25  5:16 Sam James
2022-11-14 22:15 Patrick McLean
2022-11-03 20:59 Patrick McLean
2022-10-31 18:07 Patrick McLean
2022-10-31 17:50 Patrick McLean
2022-08-01 18:56 Zac Medico
2022-07-28 13:59 Sam James
2022-04-09 19:48 Zac Medico

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=1652959467.cf2693904325131c795180a4ad9e79fa19444521.xen0n@gentoo \
    --to=xen0n@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