From: Stephen Hemminger <stephen@networkplumber.org>
To: David Miller <davem@davemloft.net>
Cc: dsahern@gmail.com, simon.horman@netronome.com,
daniel@iogearbox.net, phil@nwl.cc, netdev@vger.kernel.org
Subject: Re: [RFC] iproute: Add support for extended ack to rtnl_talk
Date: Mon, 7 Aug 2017 14:21:13 -0700 [thread overview]
Message-ID: <20170807142113.66347c79@xeon-e3> (raw)
In-Reply-To: <20170807.132603.2058256055534574552.davem@davemloft.net>
On Mon, 07 Aug 2017 13:26:03 -0700 (PDT)
David Miller <davem@davemloft.net> wrote:
> From: Stephen Hemminger <stephen@networkplumber.org>
> Date: Mon, 7 Aug 2017 12:12:35 -0700
>
> > Dave, I asked for test cases, and received none.
>
> You don't need a test case to type make and make sure the build succeeds.
It did succeed for libmnl but was not doing anything.
next prev parent reply other threads:[~2017-08-07 21:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 23:56 [RFC] iproute: Add support for extended ack to rtnl_talk Stephen Hemminger
2017-05-04 9:36 ` Daniel Borkmann
2017-05-04 14:27 ` David Ahern
2017-05-04 14:41 ` David Miller
2017-05-04 15:50 ` Jamal Hadi Salim
2017-05-04 16:43 ` Stephen Hemminger
2017-05-04 20:43 ` Phil Sutter
2017-05-14 1:29 ` David Ahern
2017-05-16 16:36 ` Stephen Hemminger
2017-05-18 10:02 ` Daniel Borkmann
2017-05-18 14:55 ` Stephen Hemminger
2017-05-19 4:24 ` David Ahern
2017-08-03 20:26 ` David Ahern
2017-08-04 11:31 ` Simon Horman
2017-08-04 16:47 ` Stephen Hemminger
2017-08-07 16:48 ` David Ahern
2017-08-07 18:06 ` Stephen Hemminger
2017-08-07 18:09 ` David Ahern
2017-08-07 18:45 ` David Miller
2017-08-07 19:12 ` Stephen Hemminger
2017-08-07 20:26 ` David Miller
2017-08-07 21:21 ` Stephen Hemminger [this message]
2017-05-04 14:37 ` Leon Romanovsky
2017-05-04 16:45 ` Stephen Hemminger
2017-05-04 17:55 ` Leon Romanovsky
2017-05-06 10:36 ` Jiri Pirko
2017-05-04 16:42 ` Stephen Hemminger
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=20170807142113.66347c79@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=phil@nwl.cc \
--cc=simon.horman@netronome.com \
/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.