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:21:11 +0200	[thread overview]
Message-ID: <CAHmME9pP6CodwdYVmzj_SuHzB3WmMt+Jy1H+-yvfENeKdBLWTQ@mail.gmail.com> (raw)
In-Reply-To: <20160706150845.GE2040@lud.polynome.dn42>

On Wed, Jul 6, 2016 at 5:08 PM, Baptiste Jonglez
<baptiste@bitsofnetworks.org> wrote:
> Interesting.  I found this script in LEDE:
>
>   https://git.lede-project.org/?p=source.git;a=blob;f=scripts/strip-kmod.sh;hb=HEAD

Cool script. I'll play with it when I get home. It's possible that it
doesn't do enough, though. WireGuard is split into several files, so
there are some non-static function. But, those functions aren't in use
elsewhere in the kernel -- they shouldn't be exported. So it's a
matter of tuning things so that these symbols are removed. Will get
back to you on this...

      reply	other threads:[~2016-07-06 15:21 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
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 [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=CAHmME9pP6CodwdYVmzj_SuHzB3WmMt+Jy1H+-yvfENeKdBLWTQ@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.