From: Eric Dumazet <eric.dumazet@gmail.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, bhutchings@solarflare.com
Subject: Re: [PATCH v3] drop_monitor: convert to modular building
Date: Wed, 30 May 2012 07:29:20 +0200 [thread overview]
Message-ID: <1338355760.2760.8.camel@edumazet-glaptop> (raw)
In-Reply-To: <20120529193348.GB9258@hmsreliant.think-freely.org>
On Tue, 2012-05-29 at 15:33 -0400, Neil Horman wrote:
> Eric,
> Just FYI, I sent a series upstream to implement autoloading of generic
> netlink families. Please be awarem, that I've tested these with a hacked
> version of dropwatch, and it works great, but with the normal version of
> dropwatch, the drop_monitor module still doesn't autoload. This is due to libnl
> not explicitly requesting a family when genl_ctrl_family_resolve is called.
> Instead of trying to load the module, it dumps the existing registered families
> via a NLM_F_DUMP message. I'm working on updating libnl to correct this
> currently and will cc you on the patch.
Excellent, thanks Neil
prev parent reply other threads:[~2012-05-30 5:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 14:27 [PATCH] drop_monitor: convert to modular building Neil Horman
2012-05-16 14:48 ` Eric Dumazet
2012-05-16 15:16 ` Neil Horman
2012-05-16 15:01 ` Ben Hutchings
2012-05-16 15:19 ` Neil Horman
2012-05-16 15:34 ` Ben Hutchings
2012-05-17 17:49 ` [PATCH v2] " Neil Horman
2012-05-17 18:14 ` Ben Hutchings
2012-05-17 19:33 ` Neil Horman
2012-05-17 20:04 ` [PATCH v3] " Neil Horman
2012-05-17 20:08 ` Ben Hutchings
2012-05-17 20:09 ` David Miller
2012-05-17 20:21 ` Neil Horman
2012-05-22 13:05 ` Eric Dumazet
2012-05-22 13:57 ` Neil Horman
2012-05-29 19:33 ` Neil Horman
2012-05-30 5:29 ` Eric Dumazet [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=1338355760.2760.8.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.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