On Wed, Apr 07, 2021 at 07:17:44PM +0200, Paul Bolle wrote:
> Don Zickus schreef op wo 07-04-2021 om 12:38 [-0400]:
> > I welcome any feedback as someone who tried to help. :-D
>
> Well, I've just done my first web-based merge-request. (Actually my first
> merge-request ever. E-mailing patches is
Don Zickus schreef op wo 07-04-2021 om 12:38 [-0400]:
> I welcome any feedback as someone who tried to help. :-D
Well, I've just done my first web-based merge-request. (Actually my first
merge-request ever. E-mailing patches is so much easier!) Just to get to know
gitlab and kernel-ark. Lots of
From: Don Zickus on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/987#note_546885805
grr. thanks! updated!
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to
From: Don Zickus
[redhat] Update configs for mod-internal.list
Several of the options for mod-internal.list are now out of sync
with RHEL8. Adjust accordingly.
Cc: Waiman Long
Cc: Jiri Benc
Signed-off-by: Laura Abbott
Signed-off-by: Don Zickus
V2: rebase to latest
V3: Adjust
On Wed, Apr 07, 2021 at 04:14:28PM +0200, Paul Bolle wrote:
> Don Zickus schreef op di 06-04-2021 om 10:30 [-0400]:
> > To me, duplicates meant that same config setting in fedora and (common or
> > ark).
>
> common is for settings that are identical in fedora and ark, right?
Yeah, in theory,
From: Don Zickus on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/995#note_546859655
Only if you set up a mirror is that true. And only select projects are
allowed to be mirrored. Public project and a Silver tier, I think are
the minimum requirements. Which kernel-ark
From: Herton R. Krzesinski on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/987#note_546764458
Don, looks you are adding dmatest to the second line in the list, but
there is already an entry for it on the first line.
___
kernel
Don Zickus schreef op di 06-04-2021 om 10:30 [-0400]:
> To me, duplicates meant that same config setting in fedora and (common or
> ark).
common is for settings that are identical in fedora and ark, right?
If so, I used to have a local patch to merge.pl. It warned about pointless
overrides
From: Ondrej Mosnáček on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/994#note_546565332
I think it's common practice to resend the patch with `[PATCH RESEND]`
subject tag in such cases (with a note why you're resending). When it's
just one small patch it shouldn't bother
From: Hangbin Liu on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/994#note_546544956
I only posted to netdev. Is it OK to cc linux-crypto after post?
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send
From: Ondrej Mosnáček on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/994#note_546539113
Do you have a link? I can't see it on linux-cry...@vger.kernel.org,
which I'm subscribed to (would be nice to CC that list as well).
___
From: Hangbin Liu on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/994#note_546522526
Make sense to me, I just post a patch to upstream.
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to
From: Herbert Xu on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/993#note_546486460
Acked-by: Herbert Xu
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to
From: Jiri Benc on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/987#note_546473354
Looks good. Thanks!
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to
From: Jiri Benc on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/994#note_546471110
That's a good point. I agree that this should be submitted upstream
first.
___
kernel mailing list -- kernel@lists.fedoraproject.org
To
From: Ondrej Mosnáček on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/994#note_546448417
I just wonder if it wouldn't make sense to push [a variant of] this
patch also upstream? The relation between Wireguard and FIPS mode
doesn't seem distro-specific. Or does upstream
From: Hangbin Liu on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/994#note_546433292
@marcelo.leitner Sorry, I set the notification to only mentioned. I have
updated the patch. Please help review.
___
kernel mailing list --
From: Hangbin Liu
wireguard: disable in FIPS mode
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1940794
Upstream: RHEL Only
As the cryptos(BLAKE2S, Curve25519, CHACHA20POLY1305) in WireGuard are not
FIPS certified, the WireGuard module should be disabled in FIPS mode.
Signed-off-by:
From: Hangbin Liu on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/993#note_546425260
@omos Thanks, I have updated the subject. Would you please help ack the
bug if it's OK for you?
___
kernel mailing list --
From: Hangbin Liu
wireguard: mark as Tech Preview
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1613522
Upstream: RHEL only
WireGuard is Tech Preview in RHEL 9.0.
Signed-off-by: Hangbin Liu
diff a/drivers/net/wireguard/main.c b/drivers/net/wireguard/main.c
---
From: Hangbin Liu
configs: enable CONFIG_WIREGUARD in ARK
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1613522
Upstream: RHEL only
Enable CONFIG_WIREGUARD as requested in the bugzilla. Configs
CONFIG_CRYPTO_LIB_BLAKE2S, CONFIG_CRYPTO_LIB_CHACHA20POLY1305,
CONFIG_CRYPTO_LIB_CURVE25519
From: Hangbin Liu on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/993
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1613522
Upstream: RHEL only
Enable CONFIG_WIREGUARD as requested in the bugzilla. Configs
CONFIG_CRYPTO_LIB_BLAKE2S,
22 matches
Mail list logo
