mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH v2 1/5] libnftnl: Upgrade from 1.0.6 to 1.0.9
Date: Fri,  6 Apr 2018 11:07:26 +0200	[thread overview]
Message-ID: <20180406090730.2055-2-ada@thorsis.com> (raw)
In-Reply-To: <20180406090730.2055-1-ada@thorsis.com>

The upgrades include support for newer kernel features and bugfixes.
This is a dependency for nftables 0.8.3. See the announcements for
details:

* 1.0.7: https://lists.netfilter.org/pipermail/netfilter-announce/2016/000221.html
* 1.0.8: https://lists.netfilter.org/pipermail/netfilter-announce/2017/000224.html
* 1.0.9: https://lists.netfilter.org/pipermail/netfilter-announce/2018/000226.html

Signed-off-by: Alexander Dahl <ada@thorsis.com>
---
 rules/libnftnl.in   | 6 ------
 rules/libnftnl.make | 5 ++---
 2 files changed, 2 insertions(+), 9 deletions(-)

diff --git a/rules/libnftnl.in b/rules/libnftnl.in
index 7d91ccea8e..78cefc2cbd 100644
--- a/rules/libnftnl.in
+++ b/rules/libnftnl.in
@@ -3,7 +3,6 @@
 menuconfig LIBNFTNL
 	tristate
 	select LIBMNL
-	select LIBMXML if LIBNFTNL_XML
 	select JANSSON if LIBNFTNL_JSON
 	prompt "libnftnl                      "
 	help
@@ -14,11 +13,6 @@ menuconfig LIBNFTNL
 
 if LIBNFTNL
 
-config LIBNFTNL_XML
-	bool
-	depends on LIBNFTNL
-	prompt "XML parsing support"
-
 config LIBNFTNL_JSON
 	bool
 	depends on LIBNFTNL
diff --git a/rules/libnftnl.make b/rules/libnftnl.make
index 7d73a21946..5547b56bff 100644
--- a/rules/libnftnl.make
+++ b/rules/libnftnl.make
@@ -16,8 +16,8 @@ PACKAGES-$(PTXCONF_LIBNFTNL) += libnftnl
 #
 # Paths and names
 #
-LIBNFTNL_VERSION	:= 1.0.6
-LIBNFTNL_MD5	:= 6d7f9f161538ca7efd535dcc70caf964
+LIBNFTNL_VERSION	:= 1.0.9
+LIBNFTNL_MD5	:= 6c4f392faab5745933553b4354be5d8d
 LIBNFTNL		:= libnftnl-$(LIBNFTNL_VERSION)
 LIBNFTNL_SUFFIX	:= tar.bz2
 LIBNFTNL_URL		:= http://ftp.netfilter.org/pub/libnftnl/$(LIBNFTNL).$(LIBNFTNL_SUFFIX)
@@ -31,7 +31,6 @@ LIBNFTNL_LICENSE	:= GPL-2.0-only
 LIBNFTNL_CONF_TOOL	:= autoconf
 LIBNFTNL_CONF_OPT	:= \
 	$(CROSS_AUTOCONF_USR) \
-	--$(call ptx/wwo, PTXCONF_LIBNFTNL_XML)-xml-parsing \
 	--$(call ptx/wwo, PTXCONF_LIBNFTNL_JSON)-json-parsing
 
 # ----------------------------------------------------------------------------
-- 
2.11.0


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2018-04-06  9:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-06  9:07 [ptxdist] [PATCH v2 0/5] netfilter: Upgrades and autostart Alexander Dahl
2018-04-06  9:07 ` Alexander Dahl [this message]
2018-04-06  9:07 ` [ptxdist] [PATCH v2 2/5] nftables: Upgrade from v0.6 to v0.8.3 Alexander Dahl
2018-04-06  9:48   ` Alexander Dahl
2018-04-06  9:07 ` [ptxdist] [PATCH v2 3/5] nftables: Fix Vim modelines Alexander Dahl
2018-04-10  8:47   ` Michael Olbrich
2018-04-10  9:02     ` Alexander Dahl
2018-04-10 14:03       ` Michael Olbrich
2018-04-06  9:07 ` [ptxdist] [PATCH v2 4/5] nftables: Add example config file Alexander Dahl
2018-04-06  9:07 ` [ptxdist] [PATCH v2 5/5] nftables: Add bbinit startscript Alexander Dahl
2018-04-09  8:30   ` Michael Olbrich
2018-04-09  9:16     ` Alexander Dahl
2018-04-10  6:57     ` Alexander Dahl
2018-04-10  8:42       ` Michael Olbrich

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=20180406090730.2055-2-ada@thorsis.com \
    --to=ada@thorsis.com \
    --cc=ptxdist@pengutronix.de \
    /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