mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wim Van Sebroeck <wim@iguana.be>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel@vger.kernel.org, Nicolas Thill <nico@openwrt.org>,
	Heiko Ronsdorf <hero@ihg.uni-duisburg.de>,
	Rodolfo Giometti <giometti@ascensit.com>,
	Andrey Panin <pazke@donpac.ru>, Guido Guenther <agx@sigxcpu.org>,
	Curt E Bruns <curt.e.bruns@intel.com>,
	Deepak Saxena <dsaxena@plexity.net>,
	Andrew Victor <linux@maxim.org.za>,
	"George G. Davis" <gdavis@mvista.com>,
	Sylver Bruneau <sylver.bruneau@googlemail.com>,
	linux-watchdog@vger.kernel.org
Subject: Re: [PATCH 1/2 (resend)] watchdog: Use DEFINE_SPINLOCK() for static spinlocks
Date: Tue, 29 Nov 2011 12:21:57 +0100	[thread overview]
Message-ID: <20111129112157.GJ23376@infomag.iguana.be> (raw)
In-Reply-To: <1322546041.9040.1.camel@phoenix>

Hi Alex,

> Rather than just defining static spinlock_t variables and then
> initializing them later in init functions, simply define them with
> DEFINE_SPINLOCK() and remove the calls to spin_lock_init().
> 
> Cc: Wim Van Sebroeck <wim@iguana.be>
> Cc: Nicolas Thill <nico@openwrt.org>
> Cc: Heiko Ronsdorf <hero@ihg.uni-duisburg.de>
> Cc: Rodolfo Giometti <giometti@ascensit.com>
> Cc: Andrey Panin <pazke@donpac.ru>
> Cc: Guido Guenther <agx@sigxcpu.org>
> Cc: Curt E Bruns <curt.e.bruns@intel.com>
> Cc: Deepak Saxena <dsaxena@plexity.net>
> Cc: Andrew Victor <linux@maxim.org.za>
> Cc: George G. Davis <gdavis@mvista.com>
> Cc: Sylver Bruneau <sylver.bruneau@googlemail.com>
> Signed-off-by: Axel Lin <axel.lin@gmail.com>

Added to the linux-next branch of the watchdog tree.

Kind regards,
Wim.


      parent reply	other threads:[~2011-11-29 11:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-29  5:54 Axel Lin
2011-11-29  5:56 ` [PATCH 2/2] watchdog: convert drivers/watchdog/* to use module_platform_driver() Axel Lin
2011-11-29 11:23   ` Wim Van Sebroeck
2011-11-29 11:21 ` Wim Van Sebroeck [this message]

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=20111129112157.GJ23376@infomag.iguana.be \
    --to=wim@iguana.be \
    --cc=agx@sigxcpu.org \
    --cc=axel.lin@gmail.com \
    --cc=curt.e.bruns@intel.com \
    --cc=dsaxena@plexity.net \
    --cc=gdavis@mvista.com \
    --cc=giometti@ascensit.com \
    --cc=hero@ihg.uni-duisburg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@maxim.org.za \
    --cc=nico@openwrt.org \
    --cc=pazke@donpac.ru \
    --cc=sylver.bruneau@googlemail.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

all inboxes | Powered by JetHome®