From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3 1/1] netns_netlink: Rewrite into new API
Date: Tue, 11 May 2021 16:05:01 +0200 [thread overview]
Message-ID: <YJqPDb5WGhNTtLfB@pevik> (raw)
In-Reply-To: <YJp9/JHow8g5Xt/K@yuki>
Hi Cyril,
> Hi!
> Looks good: Reviewed-by: Cyril Hrubis <chrubis@suse.cz>
Thanks!
> Also this is a bugfix for new iproute, right? If so this should get in
> before the release.
Yes, thus pushed.
> And we should probably make use of the netlink library from Martin later
> on, but that can wait after the release.
+1, put into my TODO list.
Also how about keeping libmnl vs. using Martin's library for
route-change-netlink.c? Which one is better to use?
(already asked in [1]: it'd be nice to get rid of libmnl dependency,
but on the other hand using it means also testing it).
Kind regards,
Petr
[1] https://lists.linux.it/pipermail/ltp/2021-May/022529.html
prev parent reply other threads:[~2021-05-11 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 12:56 [LTP] [PATCH v3 1/1] netns_netlink: Rewrite into new API Petr Vorel
2021-05-11 12:52 ` Cyril Hrubis
2021-05-11 14:05 ` Petr Vorel [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=YJqPDb5WGhNTtLfB@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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