linux-bcache.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kent Overstreet <koverstreet@google.com>
To: linux-bcache@vger.kernel.org, linux-kernel@vger.kernel.org,
	dm-devel@redhat.com
Cc: tj@kernel.org, joe@perches.com,
	Kent Overstreet <koverstreet@google.com>,
	vgoyal@redhat.com
Subject: [Bcache v15 02/16] Fix ratelimit macro to compile in c99 mode
Date: Mon, 23 Jul 2012 16:50:45 -0700	[thread overview]
Message-ID: <1343087459-17645-3-git-send-email-koverstreet@google.com> (raw)
In-Reply-To: <1343087459-17645-1-git-send-email-koverstreet@google.com>


Signed-off-by: Kent Overstreet <koverstreet@google.com>
---
 include/linux/ratelimit.h |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/include/linux/ratelimit.h b/include/linux/ratelimit.h
index e11ccb4..9ad57d3 100644
--- a/include/linux/ratelimit.h
+++ b/include/linux/ratelimit.h
@@ -20,7 +20,7 @@ struct ratelimit_state {
 #define DEFINE_RATELIMIT_STATE(name, interval_init, burst_init)		\
 									\
 	struct ratelimit_state name = {					\
-		.lock		= __RAW_SPIN_LOCK_UNLOCKED(name.lock),	\
+		.lock		= __RAW_SPIN_LOCK_INITIALIZER(name.lock),\
 		.interval	= interval_init,			\
 		.burst		= burst_init,				\
 	}
-- 
1.7.7.3

  parent reply	other threads:[~2012-07-23 23:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-23 23:50 [Bcache v15 00/16] Kent Overstreet
2012-07-23 23:50 ` [Bcache v15 01/16] Revert "rw_semaphore: remove up/down_read_non_owner" Kent Overstreet
2012-07-23 23:50 ` Kent Overstreet [this message]
2012-07-23 23:50 ` [Bcache v15 03/16] Export get_random_int() Kent Overstreet
2012-07-23 23:50 ` [Bcache v15 04/16] Export blk_fill_rwbs() Kent Overstreet
2012-07-23 23:50 ` [Bcache v15 05/16] Export __lockdep_no_validate__ Kent Overstreet
2012-07-23 23:50 ` [Bcache v15 06/16] Add human-readable units modifier to vsnprintf() Kent Overstreet
2012-07-23 23:50 ` [Bcache v15 08/16] bcache: Generic utility code Kent Overstreet
2012-07-23 23:50 ` [Bcache v15 09/16] bcache: Documentation, and changes to generic code Kent Overstreet
2012-07-23 23:50 ` [Bcache v15 11/16] bcache: Core btree code Kent Overstreet
2012-07-23 23:50 ` [Bcache v15 13/16] bcache: Journalling Kent Overstreet
2012-07-23 23:50 ` [Bcache v15 14/16] bcache: Request, io and allocation code Kent Overstreet
     [not found] ` <1343087459-17645-1-git-send-email-koverstreet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2012-07-23 23:50   ` [Bcache v15 07/16] Closures Kent Overstreet
     [not found]     ` <1343087459-17645-8-git-send-email-koverstreet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2012-07-23 23:55       ` Kent Overstreet
2012-07-24 16:04         ` Alex Elsayed
2012-07-25  6:31           ` Kent Overstreet
2012-07-23 23:50   ` [Bcache v15 10/16] bcache: Superblock/initialization/sysfs code Kent Overstreet
2012-07-23 23:50   ` [Bcache v15 12/16] bcache: Bset code (lookups within a btree node) Kent Overstreet
2012-07-23 23:50   ` [Bcache v15 15/16] bcache: Writeback, copying garbage collection Kent Overstreet
2012-07-23 23:50 ` [Bcache v15 16/16] bcache: Debug and tracing code Kent Overstreet

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=1343087459-17645-3-git-send-email-koverstreet@google.com \
    --to=koverstreet@google.com \
    --cc=dm-devel@redhat.com \
    --cc=joe@perches.com \
    --cc=linux-bcache@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@kernel.org \
    --cc=vgoyal@redhat.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;
as well as URLs for NNTP newsgroup(s).