From: Vagrant Cascadian <vagrant@debian.org>
To: 宋文武 <iyzsong@member.fsf.org>,
"Danny Milosavljevic" <dannym@scratchpost.org>
Cc: 37398@debbugs.gnu.org
Subject: [bug#37398] [PATCH 1/2] gnu: linux-libre: Enable all nftables family modules.
Date: Sun, 22 Sep 2019 17:04:44 -0700 [thread overview]
Message-ID: <87ftknvpwj.fsf@yucca> (raw)
In-Reply-To: <87ef0hrhux.fsf@member.fsf.org>
[-- Attachment #1: Type: text/plain, Size: 799 bytes --]
On 2019-09-15, 宋文武 wrote:
> Danny Milosavljevic <dannym@scratchpost.org> writes:
> 5.2-arm-veyron.conf is skipped, CC to Timothy and Vagrant, is it worth
> to enable nftables for the "veyron" chromebooks? Unlike other kernel
> configs, this one doesn't have most netfilter (eg: iptables) options
> enabled.
It would certainly be worth adding; unfortunately I haven't gotten a
working kernel since the upgrade from 5.1.x to 5.2.x... so haven't been
able to test it.
Even better, getting the "regular" arm kernel working on the
veyron... but I haven't tried that in a while.
I've also been looking at syncing some new board support and features
from the Debian arm and arm64 kernel configurations, but there is a fair
amount of diff to go over...
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-09-23 0:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 10:06 [bug#37398] [PATCH 0/2]: services: Add nftables-service-type 宋文武
2019-09-13 10:17 ` [bug#37398] [PATCH 1/2] gnu: linux-libre: Enable all nftables family modules 宋文武
2019-09-13 10:17 ` [bug#37398] [PATCH 2/2] services: Add nftables-service-type 宋文武
2019-09-13 14:06 ` [bug#37398] [PATCH 1/2] gnu: linux-libre: Enable all nftables family modules 宋文武
2019-09-13 15:41 ` Marius Bakke
2019-09-14 4:02 ` 宋文武
2019-09-14 10:02 ` Danny Milosavljevic
2019-09-15 10:09 ` 宋文武
2019-09-23 0:04 ` Vagrant Cascadian [this message]
2019-09-18 11:05 ` bug#37398: [PATCH 0/2]: services: Add nftables-service-type 宋文武
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=87ftknvpwj.fsf@yucca \
--to=vagrant@debian.org \
--cc=37398@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=iyzsong@member.fsf.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.