From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2, 1/1] package/connman: disable wireguard support
Date: Thu, 26 Mar 2020 21:43:56 +0100 [thread overview]
Message-ID: <20200326204356.GX22325@scaer> (raw)
In-Reply-To: <20200326203735.GW22325@scaer>
Romain, Mikael, All,
On 2020-03-26 21:37 +0100, Yann E. MORIN spake thusly:
> On 2020-03-26 21:30 +0100, Romain Naour spake thusly:
> > Le 26/03/2020 ? 20:01, Yann E. MORIN a ?crit?:
> > > On 2020-03-26 16:25 +0100, Mikael Bourhis-Cloarec spake thusly:
> > >> The new Connman 1.38 release uses 'WireGuard' and 'libmnl' by default now.
> Damn, iptables, not nftables. Your patch is still on the table, then.
In the meantime, Thomas applied another earlier pending patch that
actually enabled wireguard support.
So I've marked your patch as not applicable in patchwork.
Thanks for the contribution nonetheless! :-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2020-03-26 20:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 15:25 [Buildroot] [PATCH v2, 1/1] package/connman: disable wireguard support Mikael Bourhis-Cloarec
2020-03-26 17:01 ` Romain Naour
2020-03-26 19:01 ` Yann E. MORIN
2020-03-26 20:30 ` Romain Naour
2020-03-26 20:37 ` Yann E. MORIN
2020-03-26 20:43 ` Yann E. MORIN [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=20200326204356.GX22325@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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.