From: David Miller <davem@davemloft.net>
To: idosch@idosch.org
Cc: netdev@vger.kernel.org, nhorman@tuxdriver.com, toke@redhat.com,
jiri@mellanox.com, dsahern@gmail.com, mlxsw@mellanox.com,
idosch@mellanox.com
Subject: Re: [PATCH net-next 0/6] drop_monitor: Various improvements and cleanups
Date: Tue, 06 Aug 2019 12:38:22 -0700 (PDT) [thread overview]
Message-ID: <20190806.123822.1326315361107457509.davem@davemloft.net> (raw)
In-Reply-To: <20190806131956.26168-1-idosch@idosch.org>
From: Ido Schimmel <idosch@idosch.org>
Date: Tue, 6 Aug 2019 16:19:50 +0300
> From: Ido Schimmel <idosch@mellanox.com>
>
> This patchset performs various improvements and cleanups in drop monitor
> with no functional changes intended. There are no changes in these
> patches relative to the RFC I sent two weeks ago [1].
>
> A followup patchset will extend drop monitor with a packet alert mode in
> which the dropped packet is notified to user space instead of just a
> summary of recent drops. Subsequent patchsets will add the ability to
> monitor hardware originated drops via drop monitor.
>
> [1] https://patchwork.ozlabs.org/cover/1135226/
These all look fine to me, series applied.
Thanks.
prev parent reply other threads:[~2019-08-06 19:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 13:19 [PATCH net-next 0/6] drop_monitor: Various improvements and cleanups Ido Schimmel
2019-08-06 13:19 ` [PATCH net-next 1/6] drop_monitor: Use correct error code Ido Schimmel
2019-08-06 13:19 ` [PATCH net-next 2/6] drop_monitor: Rename and document scope of mutex Ido Schimmel
2019-08-06 13:19 ` [PATCH net-next 3/6] drop_monitor: Document scope of spinlock Ido Schimmel
2019-08-06 13:19 ` [PATCH net-next 4/6] drop_monitor: Avoid multiple blank lines Ido Schimmel
2019-08-06 13:19 ` [PATCH net-next 5/6] drop_monitor: Add extack support Ido Schimmel
2019-08-06 13:19 ` [PATCH net-next 6/6] drop_monitor: Use pre_doit / post_doit hooks Ido Schimmel
2019-08-06 19:38 ` David Miller [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=20190806.123822.1326315361107457509.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=idosch@idosch.org \
--cc=idosch@mellanox.com \
--cc=jiri@mellanox.com \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=toke@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 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).