Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Thadeu Lima de Souza Cascardo <cascardo@canonical.com>
To: wireguard@lists.zx2c4.com
Cc: Thadeu Lima de Souza Cascardo <cascardo@canonical.com>
Subject: [PATCH 0/1] wireguard-linux-compat: fix build on Ubuntu 18.04
Date: Fri, 23 Apr 2021 14:19:37 -0300	[thread overview]
Message-ID: <20210423171938.583964-1-cascardo@canonical.com> (raw)

Back in February, we were looking into backporting a commit to Ubuntu 18.04 GA
kernel that introduces skb_mark_not_on_list.

That would break wireguard-linux-compat when building against that kernel, so a
change was submitted as that commit would be introduced soon.

However, that plan did not work out as intended, and since then,
wireguard-linux-compat CI has been broken on Ubuntu 18.04.

Jason, thanks for bringing that up to our attention, and sorry that we broke
wireguard-linux-compat CI.

We will resend a fix as soon as we sort out when that commit will be applied.

Thanks.
Cascardo.

Thadeu Lima de Souza Cascardo (1):
  Revert "compat: skb_mark_not_on_list will be backported to Ubuntu
    18.04"

 src/compat/compat.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.27.0


             reply	other threads:[~2021-04-23 17:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-23 17:19 Thadeu Lima de Souza Cascardo [this message]
2021-04-23 17:19 ` [PATCH 1/1] Revert "compat: skb_mark_not_on_list will be backported to Ubuntu 18.04" Thadeu Lima de Souza Cascardo
2021-04-23 20:33   ` Jason A. Donenfeld
2021-04-23 20:32 ` [PATCH 0/1] wireguard-linux-compat: fix build on Ubuntu 18.04 Jason A. Donenfeld

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=20210423171938.583964-1-cascardo@canonical.com \
    --to=cascardo@canonical.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).