All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Baptiste Jonglez <baptiste@bitsofnetworks.org>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] OpenWRT package for wireguard
Date: Wed, 6 Jul 2016 17:16:42 +0200	[thread overview]
Message-ID: <CAHmME9rCa3L2eBdrVgZhhhmHQbdswX0BUDXo=YD-AYzoE-Wq8Q@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9of2XeH-7mJF-Avq_n1SPQwesH-zkk-0Nx8ff1ef3f5jA@mail.gmail.com>

There's also a lot to be done with -flto. I was working on getting
this working last year but ran into some snags. I'll give it another
try.

There's also the more bootleg version of running with -fwhole-program
and then using the __visible attribute on the module init/cleanup
functions. I don't know if this would actually work properly though.

  reply	other threads:[~2016-07-06 15:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29 11:24 [WireGuard] OpenWRT package for wireguard Baptiste Jonglez
2016-07-02 10:27 ` Baptiste Jonglez
2016-07-02 10:43   ` [WireGuard] Kernel symbol dependencies and KCONFIG usage for kernel packages Baptiste Jonglez
2016-07-02 10:54   ` [WireGuard] OpenWRT package for wireguard Jason A. Donenfeld
2016-07-04  7:48 ` Baptiste Jonglez
2016-07-04 12:16   ` Jason A. Donenfeld
2016-07-05 22:03   ` Baptiste Jonglez
2016-07-06  9:53     ` Jason A. Donenfeld
2016-07-06  9:56       ` Jason A. Donenfeld
2016-07-06 14:54         ` Jason A. Donenfeld
2016-07-06 15:16           ` Jason A. Donenfeld [this message]
2016-07-10 17:21           ` Baptiste Jonglez
2016-07-10 17:52             ` Jason A. Donenfeld
2016-07-10 17:56               ` Baptiste Jonglez
2016-07-06 15:08         ` Baptiste Jonglez
2016-07-06 15:21           ` 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='CAHmME9rCa3L2eBdrVgZhhhmHQbdswX0BUDXo=YD-AYzoE-Wq8Q@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=baptiste@bitsofnetworks.org \
    --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.