[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20120529.223434.508811240180990047.davem@davemloft.net>
Date: Tue, 29 May 2012 22:34:34 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: nhorman@...driver.com
Cc: netdev@...r.kernel.org, eric.dumazet@...il.com,
jchapman@...alix.com
Subject: Re: [PATCH 0/3] net: implement auto-loading of generic netlink
modules
From: Neil Horman <nhorman@...driver.com>
Date: Tue, 29 May 2012 15:30:39 -0400
>
> Eric D. recently noted that the drop_monitor module didn't autoload when the
> dropwatch user space utility started. Looking into this I noted that theres no
> formal macro set to define module aliases that can be used by a request module
> call in the generic netlink family lookup path. Currenlty the
> net-pf-*-proto-*-type-<n> format is used, but the macros which form this expect
> <n> to be a well defined integer, which generic netlink doesn't use for family
> definitions. So this series creates a new macro that create a
> net-pf-*-proto-*-name format where name can be any arbitrary string, allowing us
> to apend family-<x> where x is a generic netlink family name. With these
> macros, we can easily autoload modules that register generic netlink families
>
> Signed-off-by: Neil Horman <nhorman@...driver.com>
Looks great, all applied, thanks Neil.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists