public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
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: Tue, 22 May 2012 15:05:19 +0200	[thread overview]
Message-ID: <1337691919.3361.189.camel@edumazet-glaptop> (raw)
In-Reply-To: <20120517202152.GB19321@hmsreliant.think-freely.org>

On Thu, 2012-05-17 at 16:21 -0400, Neil Horman wrote:
> On Thu, May 17, 2012 at 04:09:37PM -0400, David Miller wrote:

> > 
> > Applied, althrough it didn't apply cleanly to net-next.
> > 
> 
> Apologies Dave, should have told you that I was carrying Joe P.'s cleanup patch
> in my net-next tree as well:
> http://marc.info/?l=linux-netdev&m=133727344816140&w=2
> 
> Since you noted that you had applied it, I applied it myself here.
> Neil
> 

Any plan to autoload drop_monitor module from dropwatch,
or issuing some advice ?

# dropwatch -l kas
Unable to find NET_DM family, dropwatch can't work
Cleanuing up on socket creation error

Thanks

  reply	other threads:[~2012-05-22 13:05 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 [this message]
2012-05-22 13:57         ` Neil Horman
2012-05-29 19:33         ` Neil Horman
2012-05-30  5:29           ` Eric Dumazet

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=1337691919.3361.189.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