From: Stephen Hemminger <stephen@networkplumber.org>
To: Vadim Kochan <vadim4j@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] ip monitor: Fixed printing timestamp few times
Date: Wed, 3 Dec 2014 09:13:38 -0800 [thread overview]
Message-ID: <20141203091338.2d32de2c@urahara> (raw)
In-Reply-To: <1417389262-25189-1-git-send-email-vadim4j@gmail.com>
On Mon, 1 Dec 2014 01:14:22 +0200
Vadim Kochan <vadim4j@gmail.com> wrote:
> Another fix when timestamp is printed few times
> before the event message.
>
> Fixed by skipping the message types which are not supported.
>
> Signed-off-by: Vadim Kochan <vadim4j@gmail.com>
I don't see how you could get into accept_msg and cause this.
The filtering should already be done by kernel for most things.
The code already filters TC messages in kernel. Other types
should be done as well.
Ps: this code is crying to be a switch statement.
next prev parent reply other threads:[~2014-12-03 17:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 23:14 [PATCH iproute2] ip monitor: Fixed printing timestamp few times Vadim Kochan
2014-12-03 17:13 ` Stephen Hemminger [this message]
2014-12-03 17:11 ` vadim4j
2014-12-03 17:47 ` Stephen Hemminger
2014-12-03 17:41 ` vadim4j
2014-12-04 21:43 ` Vadim Kochan
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=20141203091338.2d32de2c@urahara \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=vadim4j@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).