From: David Ahern <dsahern@gmail.com>
To: Serhey Popovych <serhe.popovych@gmail.com>, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next 0/9] ipaddress: Make print_linkinfo_brief() static
Date: Wed, 14 Feb 2018 13:20:10 -0700 [thread overview]
Message-ID: <0e6aca0c-9f6f-41d1-76e5-7737a90aa669@gmail.com> (raw)
In-Reply-To: <9e6c4e39-6ecc-cd59-a980-1b299a5a6cb2@gmail.com>
On 2/14/18 1:09 PM, Serhey Popovych wrote:
>
> Any comments on this series? Should I perform some additional testing?
>
>
I thought I had applied them. Can you re-send and cc me?
next prev parent reply other threads:[~2018-02-14 20:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 19:49 [PATCH iproute2-next 0/9] ipaddress: Make print_linkinfo_brief() static Serhey Popovych
2018-02-05 19:49 ` [PATCH iproute2-next 1/9] ipaddress: Abstract IFA_LABEL matching code Serhey Popovych
2018-02-05 19:49 ` [PATCH iproute2-next 2/9] ipaddress: ll_map: Replace ll_idx_n2a() with ll_index_to_name() Serhey Popovych
2018-02-05 19:49 ` [PATCH iproute2-next 3/9] utils: Reimplement ll_idx_n2a() and introduce ll_idx_a2n() Serhey Popovych
2018-02-05 19:49 ` [PATCH iproute2-next 4/9] ipaddress: Improve print_linkinfo() Serhey Popovych
2018-02-05 19:49 ` [PATCH iproute2-next 5/9] ipaddress: Simplify print_linkinfo_brief() and it's usage Serhey Popovych
2018-02-05 19:49 ` [PATCH iproute2-next 6/9] lib: Correct object file dependencies Serhey Popovych
2018-02-05 19:49 ` [PATCH iproute2-next 7/9] utils: Introduce and use get_ifname_rta() Serhey Popovych
2018-02-05 19:49 ` [PATCH iproute2-next 8/9] utils: Introduce and use print_name_and_link() to print name@link Serhey Popovych
2018-02-07 5:14 ` David Ahern
2018-02-07 7:36 ` Serhey Popovych
2018-02-07 15:59 ` David Ahern
2018-02-05 19:49 ` [PATCH iproute2-next 9/9] ipaddress: Make print_linkinfo_brief() static Serhey Popovych
2018-02-14 20:09 ` [PATCH iproute2-next 0/9] " Serhey Popovych
2018-02-14 20:20 ` David Ahern [this message]
2018-02-14 21:39 ` Serhey Popovych
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=0e6aca0c-9f6f-41d1-76e5-7737a90aa669@gmail.com \
--to=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=serhe.popovych@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).