From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] ethtool: Version bump. 6.0 -> 6.1
Date: Fri, 17 Feb 2023 18:20:23 +0100 [thread overview]
Message-ID: <20230217172023.1822036-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20230103112208.2794055-1-christian.melki@t2data.com>
Thanks, applied as 3f1c976193da808fe564c082f86f90491278f51c.
Michael
[sent from post-receive hook]
On Fri, 17 Feb 2023 18:20:22 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Minor fixes and UAPI update.
>
> * Force enable netlink interface.
> Since ethtool is already dependent on libmnl per .in-file,
> might aswell be explicit with the netlink interface.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20230103112208.2794055-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/ethtool.make b/rules/ethtool.make
> index 9150fdaea94b..dd0680e76fc4 100644
> --- a/rules/ethtool.make
> +++ b/rules/ethtool.make
> @@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_ETHTOOL) += ethtool
> #
> # Paths and names
> #
> -ETHTOOL_VERSION := 6.0
> -ETHTOOL_MD5 := 1284306e608fad9c79fa80edc288e071
> +ETHTOOL_VERSION := 6.1
> +ETHTOOL_MD5 := 99fe4294ed0e3ebeb7c949ca459e2ffd
> ETHTOOL_SUFFIX := tar.xz
> ETHTOOL := ethtool-$(ETHTOOL_VERSION)
> ETHTOOL_URL := $(call ptx/mirror, KERNEL, ../software/network/ethtool/$(ETHTOOL).$(ETHTOOL_SUFFIX))
> @@ -33,7 +33,8 @@ ETHTOOL_LICENSE_FILES := \
> ETHTOOL_CONF_TOOL := autoconf
> ETHTOOL_CONF_OPT := \
> $(CROSS_AUTOCONF_USR) \
> - --enable-pretty-dump
> + --enable-pretty-dump \
> + --enable-netlink
>
> # ----------------------------------------------------------------------------
> # Target-Install
prev parent reply other threads:[~2023-02-17 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 11:22 [ptxdist] [PATCH v2] " Christian Melki
2023-02-17 17:20 ` Michael Olbrich [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=20230217172023.1822036-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.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