All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruno Wolff III <bruno@wolff.to>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Kernel commit d35a00b8e33dab7385f724e713ae71c8be0a49f4 breaks wireguard
Date: Mon, 27 Feb 2017 14:37:27 -0600	[thread overview]
Message-ID: <20170227203727.GA9565@wolff.to> (raw)
In-Reply-To: <20170227202205.GA9124@wolff.to>

On Mon, Feb 27, 2017 at 14:22:05 -0600,
  Bruno Wolff III <bruno@wolff.to> wrote:
>
>I think Fedora already does that. The build gets further, but it looks 
>like another structure change is breaking things as well. I'll see if 
>I can verify the change and get you the commit number.
>In the meantime here is he error I am seeing:
>/home/bruno/WireGuard/src/data.c: In function ‘skb_reset’:
>/home/bruno/WireGuard/src/data.c:128:5: error: ‘struct sk_buff’ has no member named ‘tc_verd’

This changed in commit a5135bcfba7345031df45e02cd150a45add47cf8:
net-tc: convert tc_verd to integer bitfields

  reply	other threads:[~2017-02-27 20:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-27 18:04 Kernel commit d35a00b8e33dab7385f724e713ae71c8be0a49f4 breaks wireguard Bruno Wolff III
2017-02-27 20:10 ` Jason A. Donenfeld
2017-02-27 20:22   ` Bruno Wolff III
2017-02-27 20:37     ` Bruno Wolff III [this message]
2017-02-27 22:10       ` Jason A. Donenfeld
2017-02-27 22:14         ` Bruno Wolff III
2017-02-27 22:37           ` Bruno Wolff III
2017-02-27 23:03             ` Jason A. Donenfeld
2017-02-28  0:24               ` Bruno Wolff III
2017-02-28  0:51                 ` 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=20170227203727.GA9565@wolff.to \
    --to=bruno@wolff.to \
    --cc=Jason@zx2c4.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 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.