From: Jose Marinez <jedi_papi@yahoo.com>
To: Harsh Shandilya <me@msfjarvis.dev>
Cc: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>,
Mehdi Sadeghi <mx@43.yt>
Subject: Re: Shouldn't devices tethered to a device using Wireguard share the same IP?
Date: Thu, 21 May 2020 23:20:59 +0000 (UTC) [thread overview]
Message-ID: <1072606602.3100560.1590103259731@mail.yahoo.com> (raw)
In-Reply-To: <F7D8E321-F329-4639-883F-26FB1521ACB3@getmailspring.com>
Thank you. I will try it out. Fingers crossed!!!
On Thursday, May 21, 2020, 10:29:12 AM EDT, Harsh Shandilya <me@msfjarvis.dev> wrote:
On May 21 2020, at 7:52 pm, Jose Marinez <jedi_papi@yahoo.com> wrote:
> Thank you so much Harsh. What's the best way to make my kernel
> available to you? Even if you could allow me to push to the repo I
> wouldn't know where to save it.
The repo is maintained on GitHub so you will have to fork the repository
and create a pull request with your changes, help.github.com has very
beginner friendly documentation if this is your first time around this.
The process for adding a kernel is a bit involved and the documentation
isn't quite fleshed out. You can check the steps out here[1] and an
example of adding a new device to the repository here[2].
1: https://github.com/WireGuard/android-wireguard-module-builder#adding-your-phones-kernel
2: https://github.com/WireGuard/android-wireguard-module-builder/pull/3/files
next prev parent reply other threads:[~2020-05-21 23:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1587211445.2302354.1589995651547.ref@mail.yahoo.com>
2020-05-20 17:27 ` Jose Marinez
2020-05-20 17:53 ` Harsh Shandilya
2020-05-20 18:40 ` Jose Marinez
[not found] ` <81BFEC8F-2985-447E-9B08-5671682DBD3E@43.yt>
2020-05-20 20:53 ` Jose Marinez
2020-05-21 7:05 ` Harsh Shandilya
2020-05-21 14:22 ` Jose Marinez
2020-05-21 14:28 ` Harsh Shandilya
2020-05-21 23:20 ` Jose Marinez [this message]
[not found] <1911672182.4980335.1590508735704@mail.yahoo.com>
2020-05-26 16:03 ` Harsh Shandilya
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=1072606602.3100560.1590103259731@mail.yahoo.com \
--to=jedi_papi@yahoo.com \
--cc=me@msfjarvis.dev \
--cc=mx@43.yt \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).