All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruno Wolff III <bruno@wolff.to>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Working on change for: genetlink: make policy common to family
Date: Mon, 13 May 2019 16:21:10 -0500	[thread overview]
Message-ID: <20190513212110.GA31106@wolff.to> (raw)
In-Reply-To: <20190513202453.GA30656@wolff.to>

On Mon, May 13, 2019 at 15:24:53 -0500,
  Bruno Wolff III <bruno@wolff.to> wrote:
>On Mon, May 13, 2019 at 14:52:13 -0500,
> Bruno Wolff III <bruno@wolff.to> wrote:
>>Wireguard isn't building on 5.2 right now because of commit:
>>3b0f31f2b8c9fb348e4530b88f6b64f9621f83d6 genetlink: make policy common to family
>>
>>I've got Wireguard building, but need to do basic testing, then add 
>>a kernel version test in and do some other testing. If that all goes 
>>OK I'll submit a signed off patch to the list.
>>
>>It looks to be a very simple change to netlink.c, but I could have 
>>easily missed something subtle.
>
>wg (the config tool) doesn't work with my change, so there probably is 
>more needed than just moving .policy to the family structure in the 
>kernel. I'll continue looking at it, but it might need someone better 
>than me to look at it eventually.

There is also a small chance that there are multiple issues. I may need 
to test before and after the commit I identified to see if this is the 
case.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

  reply	other threads:[~2019-05-13 21:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-13 19:52 Working on change for: genetlink: make policy common to family Bruno Wolff III
2019-05-13 20:24 ` Bruno Wolff III
2019-05-13 21:21   ` Bruno Wolff III [this message]
2019-05-14 20:50     ` Bruno Wolff III
2019-05-15 10:50       ` Bruno Wolff III
2019-05-15 11:06         ` Bruno Wolff III
2019-05-15 11:18           ` Bruno Wolff III
2019-05-15 11:33             ` Bruno Wolff III
2019-05-17 11:12               ` Jason A. Donenfeld
2019-05-17 13:36                 ` Bruno Wolff III
2019-05-19 22:26                   ` Robin Kauffman

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=20190513212110.GA31106@wolff.to \
    --to=bruno@wolff.to \
    --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.