From: David Miller <davem@davemloft.net>
To: joe@perches.com
Cc: netdev@vger.kernel.org, linux-decnet-user@lists.sourceforge.net,
netfilter-devel@vger.kernel.org, netfilter@vger.kernel.org,
coreteam@netfilter.org, linux-wireless@vger.kernel.org,
dev@openvswitch.org, linux-sctp@vger.kernel.org,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC net-next 0/2] net: Use net_<level>_ratelimit
Date: Tue, 15 May 2012 13:45:31 -0400 (EDT) [thread overview]
Message-ID: <20120515.134531.530903973750646107.davem@davemloft.net> (raw)
In-Reply-To: <cover.1336981915.git.joe@perches.com>
From: Joe Perches <joe@perches.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.
next prev parent reply other threads:[~2012-05-15 17:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 7:56 [RFC net-next 0/2] net: Use net_<level>_ratelimit Joe Perches
2012-05-14 7:56 ` [RFC net-next 2/2] net: Convert net_ratelimit uses to net_<level>_ratelimited Joe Perches
2012-05-15 17:45 ` David Miller [this message]
2012-05-15 17:59 ` [RFC net-next 0/2] net: Use net_<level>_ratelimit Joe Perches
2012-05-15 18:03 ` Johannes Berg
2012-05-15 18:13 ` David Miller
2012-05-15 18:21 ` Johannes Berg
2012-05-15 18:24 ` David Miller
2012-05-15 18:29 ` Johannes Berg
2012-05-15 18:30 ` David Miller
2012-05-15 18:14 ` David Miller
2012-05-15 18:27 ` Johannes Berg
2012-05-15 18:29 ` David Miller
2012-05-15 18:40 ` Johannes Berg
2012-05-15 18:51 ` David Miller
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=20120515.134531.530903973750646107.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=coreteam@netfilter.org \
--cc=dev@openvswitch.org \
--cc=joe@perches.com \
--cc=linux-decnet-user@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
/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).