All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: daniel.wagner@suse.com
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>, faustin@fala.red
Subject: Re: Build wireguard-linux-compat on SLES15 (s390x)
Date: Wed, 20 Oct 2021 11:56:49 -0600	[thread overview]
Message-ID: <CAHmME9oL7UNWKbX3ZF-U_O+a9Kwn9gwsexzDQo9gngjhEdgc8Q@mail.gmail.com> (raw)
In-Reply-To: <YW/awIN8jqUF0DPk@falared>

Hi Daniel,

Do you think you could chime in here regarding the apparent absence of
wireguard on s390x? The thread began as a discussion of building it
yourself there, but I'm wondering why it isn't already there, seeing
as it's on the other archs.

Jason

On Wed, Oct 20, 2021 at 3:01 AM Faustin Lammler <faustin@fala.red> wrote:
>
> Hi Jason!
>
> "Jason A. Donenfeld" <Jason@zx2c4.com>,
> 19/10/2021 – 17:51:01 (-0600):
>
> > Isn't WireGuard already in the SLES kernel?
>
> My understanding is that it should, that's why I was surprised to have
> to build it. But apparently not.
>
> This may be related to a specific kernel from IBM LinuxONE cloud
> infrastructure?
>
> | $ uname -r
> | 5.3.18-24.86-default
>
> But again, my knowledge of SLES is very limited (and s390x architecture
> even more) so I don't have any idea why this was needed.
>
> I'll be happy to help you if you need me to do some tests on the
> machine.
>
> Cheers!
>
> --
> Faustin

  parent reply	other threads:[~2021-10-20 17:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-09 10:26 Build wireguard-linux-compat on SLES15 (s390x) Faustin Lammler
2021-10-19 11:01 ` Faustin Lammler
2021-10-19 12:18   ` CW
2021-10-19 23:51   ` Jason A. Donenfeld
2021-10-20  9:00     ` Faustin Lammler
2021-10-20 16:25       ` Samu Voutilainen
2021-10-21  7:44         ` Faustin Lammler
2021-10-21  8:07           ` Samu Voutilainen
2021-10-21  8:52             ` Faustin Lammler
2021-10-20 17:56       ` Jason A. Donenfeld [this message]
2021-10-21 12:37         ` Daniel Wagner

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=CAHmME9oL7UNWKbX3ZF-U_O+a9Kwn9gwsexzDQo9gngjhEdgc8Q@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=daniel.wagner@suse.com \
    --cc=faustin@fala.red \
    --cc=wireguard@lists.zx2c4.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.