From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: John Wayne <matrixman3077@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard backport to 2.6.3x kernels
Date: Wed, 31 Jan 2018 15:23:41 +0100 [thread overview]
Message-ID: <CAHmME9qShRtUKG0yrSe3fcH_1QLw7K80nsO6L9-u6ObBMW7gOw@mail.gmail.com> (raw)
In-Reply-To: <CACwd1hYUb0aGFOQoDY30a0Gsu2E-OaSHF0319x-kGbTSwov9Hg@mail.gmail.com>
Hi Igor,
It's certainly possible to backport. At the moment I'm focused on
moving the project forward with other tasks, so it's not a good use of
my time, but if you'd like to give this a stab, I'd happily take
non-invasive patches that only touch the compat/ directory. Just keep
in mind that you'll need to support all kernels in between your target
and the current minimum.
Regards,
Jason
prev parent reply other threads:[~2018-01-31 14:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 8:44 John Wayne
2018-01-31 9:03 ` Greg KH
2018-01-31 14:23 ` 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=CAHmME9qShRtUKG0yrSe3fcH_1QLw7K80nsO6L9-u6ObBMW7gOw@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=matrixman3077@gmail.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 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).