All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aaron Muir Hamilton <aaron@correspondwith.me>
To: wireguard@wut.to
Cc: wireguard@lists.zx2c4.com
Subject: Re: making wireguard work on RHEL7/etc.
Date: Mon, 26 Jun 2017 08:07:53 +0000	[thread overview]
Message-ID: <87o9tbuq7a.fsf@correspondwith.me> (raw)
In-Reply-To: <alpine.LRH.2.20.1706241613350.14074@bcny.fcbq.bet> (wireguard@wut.to's message of "Sat, 24 Jun 2017 16:18:51 +0100 (BST)")

This is bizarre, isn't the current RHEL/CentOS/Scientific Linux 7 kernel
a 3.10 series? Are these ifdefs only wrong on RHEL derivatives?

  reply	other threads:[~2017-06-26  7:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-24 15:18 making wireguard work on RHEL7/etc wireguard
2017-06-26  8:07 ` Aaron Muir Hamilton [this message]
2017-06-26  8:19   ` wireguard
2017-06-26  9:04     ` Jason A. Donenfeld
2017-06-26  9:25       ` wireguard
2017-06-26  9:57         ` Jason A. Donenfeld
2017-06-26 10:47           ` Jason A. Donenfeld
2017-06-26 19:55             ` wireguard
2017-06-27 11:02               ` Jason A. Donenfeld
2017-06-26 20:45             ` wireguard
2017-06-27 11:05               ` Jason A. Donenfeld
2017-06-27 11:38                 ` wireguard
2017-06-27 19:23                   ` Jason A. Donenfeld
2017-06-27 19:43                     ` wireguard
2017-06-27 19:59                       ` Jason A. Donenfeld
2017-06-27 20:22                         ` Jason A. Donenfeld
2017-06-27 20:52                           ` Jason A. Donenfeld
2017-06-27 21:30                             ` wireguard
2017-06-27 22:09                               ` Jason A. Donenfeld
2017-06-27  5:35           ` Andrej Kacian
2017-06-27  7:25             ` wireguard
2017-06-27  9:39               ` Andrej Kacian
2017-06-27 11:08                 ` Jason A. Donenfeld
2018-04-05 15:08                   ` Daniel Kahn Gillmor
2018-04-05 16:15                     ` Daniel Kahn Gillmor

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=87o9tbuq7a.fsf@correspondwith.me \
    --to=aaron@correspondwith.me \
    --cc=wireguard@lists.zx2c4.com \
    --cc=wireguard@wut.to \
    /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.