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: Pre 5.1-rc1 build issue
Date: Wed, 13 Mar 2019 23:08:32 -0500	[thread overview]
Message-ID: <20190314040832.GA8382@wolff.to> (raw)
In-Reply-To: <CAHmME9pfdqfW_7+_vWcN-YJcJcG7hFpBWpw8251Y_Nv5v5FxFg@mail.gmail.com>

On Wed, Mar 13, 2019 at 14:44:33 -0600,
  "Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
>On Wed, Mar 13, 2019 at 12:53 PM Bruno Wolff III <bruno@wolff.to> wrote:
>> I got something that seems to be working. So I'm good until the real fixes
>> are ready.
>
>Perhaps your [fake?!] fixes could become the real fixes if you ran
>`git send-email` to the mailing list?

I'll look at what I did to make sure I didn't make an unwanted rcu change. 
From Paul's talk it looks like there is a bit of a merger of a couple 
of rcu types to keep developers from getting confused and I think the 
unknown functions (that used to be known) should now call the non _bh 
version.

For the network include file I didn't include it any more. The correct 
fix is probably an ifdef based on kernel version or something like 
that.

So it might be useful to look at the changes I did, but I would be wary 
of committing them as is. It'll take me maybe an hour to double check 
and try it again on another system.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

      reply	other threads:[~2019-03-14  4:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13 18:38 Pre 5.1-rc1 build issue Bruno Wolff III
2019-03-13 18:52 ` Bruno Wolff III
2019-03-13 20:44   ` Jason A. Donenfeld
2019-03-14  4:08     ` Bruno Wolff III [this message]

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=20190314040832.GA8382@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.