From: "Alon Bar-Lev" <alonbl@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-fs/loop-aes/
Date: Mon, 8 Jul 2019 15:07:16 +0000 (UTC) [thread overview]
Message-ID: <1562598411.4399f7c7e65f641190c7f932e52a56356b00b4ee.alonbl@gentoo> (raw)
commit: 4399f7c7e65f641190c7f932e52a56356b00b4ee
Author: Alon Bar-Lev <alonbl <AT> gentoo <DOT> org>
AuthorDate: Mon Jul 8 15:06:23 2019 +0000
Commit: Alon Bar-Lev <alonbl <AT> gentoo <DOT> org>
CommitDate: Mon Jul 8 15:06:51 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4399f7c7
sys-fs/loop-aes: remove cpu_flags_x86_padlock local desc
Signed-off-by: Alon Bar-Lev <alonbl <AT> gentoo.org>
Package-Manager: Portage-2.3.66, Repoman-2.3.11
sys-fs/loop-aes/metadata.xml | 2 --
1 file changed, 2 deletions(-)
diff --git a/sys-fs/loop-aes/metadata.xml b/sys-fs/loop-aes/metadata.xml
index 40d08800ede..cf6f48a4973 100644
--- a/sys-fs/loop-aes/metadata.xml
+++ b/sys-fs/loop-aes/metadata.xml
@@ -9,8 +9,6 @@
<flag name="extra-ciphers">Enable extra ciphers</flag>
<flag name="keyscrub">Protects the encryption key in memory but takes
more cpu resources</flag>
- <flag name="cpu_flags_x86_padlock">Use VIA padlock instructions,
- detected at run time, code still works on non-padlock processors</flag>
</use>
<upstream>
<remote-id type="sourceforge">loop-aes</remote-id>
next reply other threads:[~2019-07-08 15:07 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 15:07 Alon Bar-Lev [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-13 5:56 [gentoo-commits] repo/gentoo:master commit in: sys-fs/loop-aes/ Sam James
2024-08-16 18:48 Arthur Zamarin
2024-05-25 6:50 Sam James
2024-05-25 6:47 Sam James
2024-05-25 6:47 Sam James
2024-05-25 6:47 Sam James
2024-03-04 7:53 Joonas Niilola
2024-01-20 20:18 Mike Pagano
2023-03-23 7:20 Sam James
2023-03-23 7:20 Sam James
2022-12-25 20:06 Sam James
2022-12-25 20:06 Sam James
2022-11-14 14:31 Joonas Niilola
2022-11-14 14:31 Joonas Niilola
2022-07-10 22:51 Sam James
2022-07-10 22:51 Sam James
2021-10-20 1:51 Sam James
2021-09-26 21:01 Sam James
2021-09-26 21:01 Sam James
2021-03-13 7:31 Joonas Niilola
2021-03-13 7:31 Joonas Niilola
2020-11-11 7:56 Joonas Niilola
2020-08-08 12:18 Mikle Kolyada
2020-07-20 13:01 Joonas Niilola
2020-06-08 13:41 Joonas Niilola
2020-06-08 13:41 Joonas Niilola
2019-03-20 22:00 Alon Bar-Lev
2019-03-14 17:30 Alon Bar-Lev
2018-09-27 23:55 Alon Bar-Lev
2018-04-19 22:20 Alon Bar-Lev
2017-12-07 17:40 Alon Bar-Lev
2017-10-07 8:22 Alon Bar-Lev
2017-05-20 17:58 Alon Bar-Lev
2017-03-25 21:46 Alon Bar-Lev
2017-02-04 1:31 Alon Bar-Lev
2016-06-11 16:44 Agostino Sarubbo
2016-05-22 18:37 Alon Bar-Lev
2015-12-23 13:50 Alon Bar-Lev
2015-10-15 14:07 Alon Bar-Lev
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=1562598411.4399f7c7e65f641190c7f932e52a56356b00b4ee.alonbl@gentoo \
--to=alonbl@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