[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20120515.134531.530903973750646107.davem@davemloft.net>
Date: Tue, 15 May 2012 13:45:31 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: joe@...ches.com
Cc: netdev@...r.kernel.org, linux-decnet-user@...ts.sourceforge.net,
netfilter-devel@...r.kernel.org, netfilter@...r.kernel.org,
coreteam@...filter.org, linux-wireless@...r.kernel.org,
dev@...nvswitch.org, linux-sctp@...r.kernel.org,
linux-nfs@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC net-next 0/2] net: Use net_<level>_ratelimit
From: Joe Perches <joe@...ches.com>
Date: Mon, 14 May 2012 00:56:24 -0700
> net_ratelimit() like __ratelimit() is too easy to misuse.
>
> Add simplifying macros similar to pr_<level>_ratelimited
> that combines the test of net_ratelimit and logging.
>
> Joe Perches (2):
> net: Add net_ratelimited_function and net_<level>_ratelimited macros
> net: Convert net_ratelimit uses to net_<level>_ratelimited
These look fine to me so I've applied them to net-next and am
sanity checking the build right now.
Thanks Joe.
--
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