All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Vladislav Yasevich <vyasevic@redhat.com>
Cc: netdev@vger.kernel.org, dsahern@gmail.com
Subject: Re: [PATCH V7 net-next iproute] ip: Add IFLA_EVENT output to ip monitor
Date: Mon, 5 Jun 2017 12:38:40 -0700	[thread overview]
Message-ID: <20170605123840.3f4f102f@xeon-e3> (raw)
In-Reply-To: <1496329276-31106-1-git-send-email-vyasevic@redhat.com>

On Thu,  1 Jun 2017 11:01:16 -0400
Vladislav Yasevich <vyasevic@redhat.com> wrote:

> Add IFLA_EVENT output so that event types can be viewed with
> 'monitor' command.  This gives a little more information for why
> a given message was received.
> 
> Signed-off-by: Vladislav Yasevich <vyasevic@redhat.com>

Applied to net-next.

      reply	other threads:[~2017-06-05 19:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-01 15:01 [PATCH V7 net-next iproute] ip: Add IFLA_EVENT output to ip monitor Vladislav Yasevich
2017-06-05 19:38 ` Stephen Hemminger [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=20170605123840.3f4f102f@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=dsahern@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=vyasevic@redhat.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.