From: Jiri Pirko <jiri@resnulli.us>
To: Vladislav Yasevich <vyasevich@gmail.com>
Cc: netdev@vger.kernel.org, roopa@cumulusnetworks.com,
dsa@cumulusnetworks.com, Vladislav Yasevich <vyasevic@redhat.com>
Subject: Re: [PATCH v4 net-next 0/2] rtnetlink: Updates to rtnetlink_event()
Date: Sat, 6 May 2017 12:51:30 +0200 [thread overview]
Message-ID: <20170506105130.GE2017@nanopsycho> (raw)
In-Reply-To: <1494017569-12869-1-git-send-email-vyasevic@redhat.com>
Fri, May 05, 2017 at 10:52:47PM CEST, vyasevich@gmail.com wrote:
>This is a version 4 series came out of the conversation that started
>as a result my first attempt to add netdevice event info to netlink messages.
>
>First is the patch to add IFLA_EVENT attribute to the netlink message. It
>supports only currently white-listed events.
>Like before, this is just an attribute that gets added to the rtnetlink
>message only when the messaged was generated as a result of a netdev event.
>In my case, this is necessary since I want to trap NETDEV_NOTIFY_PEERS
>event (also possibly NETDEV_RESEND_IGMP event) and perform certain actions
>in user space. This is not possible since the messages generated as
What are you trying to do in userspace if I may ask.
prev parent reply other threads:[~2017-05-06 10:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 20:52 [PATCH v4 net-next 0/2] rtnetlink: Updates to rtnetlink_event() Vladislav Yasevich
2017-05-05 20:52 ` [PATCH V3 net-next 1/2] rtnl: Add support for netdev event to link messages Vladislav Yasevich
2017-05-05 20:52 ` [PATCH V4 net-next 2/2] bonding: Prevent duplicate userspace notification Vladislav Yasevich
2017-05-06 10:51 ` Jiri Pirko [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=20170506105130.GE2017@nanopsycho \
--to=jiri@resnulli.us \
--cc=dsa@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=vyasevic@redhat.com \
--cc=vyasevich@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