All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Bruno Wolff III <bruno@wolff.to>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH] net/netfilter/nf_nat_core.h was removed by d2c5c103b1337f590b7edf1509a6e294bdf22402
Date: Thu, 14 Mar 2019 12:52:01 -0600	[thread overview]
Message-ID: <CAHmME9px1AuNAv30=Cz+09_-gk8WgLp6f40dFCsH-2WYnkzm+A@mail.gmail.com> (raw)
In-Reply-To: <20190314182534.23660-1-bruno@wolff.to>

On Thu, Mar 14, 2019 at 12:26 PM Bruno Wolff III <bruno@wolff.to> wrote:
>
> It looks like net/netfilter/nf_nat_core.h isn't needed any more and things
> seemed to work without it.
>
> Signed-off-by: Bruno Wolff III <bruno@wolff.to>

Thanks. Merged here with a slightly different message:
https://git.zx2c4.com/WireGuard/commit/?id=df681f4afe2e8a50cc2c1ee3af27b1f42c070472
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

  reply	other threads:[~2019-03-14 18:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-14 18:25 [PATCH] net/netfilter/nf_nat_core.h was removed by d2c5c103b1337f590b7edf1509a6e294bdf22402 Bruno Wolff III
2019-03-14 18:52 ` Jason A. Donenfeld [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-03-14  5:32 Bruno Wolff III
2019-03-14  5:24 Bruno Wolff III
2019-03-14  5:21 Bruno Wolff III
2019-03-14  5:34 ` Bruno Wolff III
2019-03-14  7:10   ` Aleksa Sarai
2019-03-14 12:41     ` Bruno Wolff III
2019-03-14 13:24       ` Luis Ressel
2019-03-14  5:14 Bruno Wolff III
2019-03-14 17:05 ` Bruno Wolff III

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='CAHmME9px1AuNAv30=Cz+09_-gk8WgLp6f40dFCsH-2WYnkzm+A@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=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.