From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v1 1/2] ethtool: version bump 5.1 -> 5.7
Date: Fri, 3 Jul 2020 11:06:45 +0200 [thread overview]
Message-ID: <20200703090645.GA24749@pengutronix.de> (raw)
In-Reply-To: <1e344c27e1f2a544357666066839aee01892369e.camel@pengutronix.de>
On Mon, Jun 29, 2020 at 11:17:29AM +0200, Lucas Stach wrote:
> Hi Oleksij,
>
> Am Montag, den 29.06.2020, 10:13 +0200 schrieb Oleksij Rempel:
> > Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> > ---
> > patches/ethtool-5.7/autogen.sh | 1 +
> > rules/ethtool.in | 1 +
> > rules/ethtool.make | 4 ++--
> > 3 files changed, 4 insertions(+), 2 deletions(-)
> > create mode 120000 patches/ethtool-5.7/autogen.sh
> >
> > diff --git a/patches/ethtool-5.7/autogen.sh b/patches/ethtool-
> > 5.7/autogen.sh
> > new file mode 120000
> > index 000000000..9f8a4cb7d
> > --- /dev/null
> > +++ b/patches/ethtool-5.7/autogen.sh
> > @@ -0,0 +1 @@
> > +../autogen.sh
> > \ No newline at end of file
>
> Why? Building from a release tarball without any patches shouldn't
> require this.
From his other patch, I'm guessing that he needed it while building from
git.
I dropped the autogen.sh no need to send this again.
Michael
> > diff --git a/rules/ethtool.in b/rules/ethtool.in
> > index 69f69d4e6..0ffe2907e 100644
> > --- a/rules/ethtool.in
> > +++ b/rules/ethtool.in
> > @@ -2,6 +2,7 @@
> > config ETHTOOL
> > tristate
> > prompt "ethtool"
> > + select LIBMNL
> > help
> > Ethtool is a GNU/Linux net driver diagnostic and tuning
> > tool.
> > diff --git a/rules/ethtool.make b/rules/ethtool.make
> > index dfeb8a735..649e3e580 100644
> > --- a/rules/ethtool.make
> > +++ b/rules/ethtool.make
> > @@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_ETHTOOL) += ethtool
> > #
> > # Paths and names
> > #
> > -ETHTOOL_VERSION := 5.1
> > -ETHTOOL_MD5 := fe774357084027e3739f17ad76cbab4d
> > +ETHTOOL_VERSION := 5.7
> > +ETHTOOL_MD5 := 3293642e58a205a834cbe5754df9c832
> > ETHTOOL_SUFFIX := tar.xz
> > ETHTOOL := ethtool-$(ETHTOOL_VERSION)
> > ETHTOOL_URL := $(call ptx/mirror, KERNEL,
> > ../software/network/ethtool/$(ETHTOOL).$(ETHTOOL_SUFFIX))
>
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
> To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2020-07-03 9:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 8:13 Oleksij Rempel
2020-06-29 8:13 ` [ptxdist] [PATCH v1 2/2] ethtool: build out-of-tree Oleksij Rempel
2020-07-03 9:08 ` Michael Olbrich
2020-07-03 9:18 ` Lucas Stach
2020-06-29 9:17 ` [ptxdist] [PATCH v1 1/2] ethtool: version bump 5.1 -> 5.7 Lucas Stach
2020-07-03 9:06 ` Michael Olbrich [this message]
2020-07-06 6:31 ` [ptxdist] [APPLIED] " 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=20200703090645.GA24749@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--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