public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Ohad Ben-Cohen <ohad@wizery.com>
Cc: linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, akpm@linux-foundation.org,
	Greg KH <greg@kroah.com>, Benoit Cousson <b-cousson@ti.com>,
	Grant Likely <grant.likely@secretlab.ca>,
	Hari Kanigeri <h-kanigeri2@ti.com>, Suman Anna <s-anna@ti.com>,
	Kevin Hilman <khilman@deeprootsystems.com>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v2 1/4] drivers: hwspinlock: add generic framework
Date: Tue, 30 Nov 2010 14:23:29 -0800	[thread overview]
Message-ID: <20101130222328.GB17222@atomide.com> (raw)
In-Reply-To: <AANLkTi=73VQeBj_M_PJO5OzJJDgWOXHkw31tN4z-nqMu@mail.gmail.com>

* Ohad Ben-Cohen <ohad@wizery.com> [101130 14:10]:
> On Tue, Nov 30, 2010 at 11:00 AM, Tony Lindgren <tony@atomide.com> wrote:
> > Do we even need the hwspin_lock variants,
> 
> I personally don't have any specific use case in mind.
> 
> It's just a simple wrapper over the _timeout variants, provided for
> API completeness, but -
> 
> > why can't we always use the hwspin_lock_timeout variants?
> 
> We can. I can just remove the _lock variants.

OK sounds good to me.

Tony

  reply	other threads:[~2010-11-30 22:23 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23 15:38 [PATCH v2 0/4] Introduce common hardware spinlock interface Ohad Ben-Cohen
2010-11-23 15:38 ` [PATCH v2 1/4] drivers: hwspinlock: add generic framework Ohad Ben-Cohen
2010-11-24  7:44   ` Kamoolkar, Mugdha
2010-11-24 19:59     ` Ohad Ben-Cohen
2010-11-25  3:59       ` David Brownell
2010-11-25  6:40         ` Ohad Ben-Cohen
2010-11-25 20:22           ` David Brownell
2010-11-26  7:34             ` Ohad Ben-Cohen
2010-11-27  1:24               ` David Brownell
2010-11-29  9:57                 ` Ohad Ben-Cohen
2010-11-25  6:05       ` Kamoolkar, Mugdha
2010-11-25 14:29         ` Ohad Ben-Cohen
2010-11-26  4:59   ` Olof Johansson
2010-11-26  7:18     ` Grant Likely
2010-11-26 21:00       ` Olof Johansson
2010-11-26  8:53     ` Ohad Ben-Cohen
2010-11-26  9:18       ` Russell King - ARM Linux
2010-11-26 10:16         ` Ohad Ben-Cohen
2010-11-26 10:45           ` Russell King - ARM Linux
2010-11-26 22:18             ` Ohad Ben-Cohen
2010-11-26 22:53               ` Russell King - ARM Linux
2010-11-29  9:46                 ` Ohad Ben-Cohen
2010-11-26 22:51       ` Olof Johansson
2010-11-29 21:31         ` Ohad Ben-Cohen
2010-11-30 19:00   ` Tony Lindgren
2010-11-30 22:20     ` Ohad Ben-Cohen
2010-11-30 22:23       ` Tony Lindgren [this message]
2010-11-23 15:38 ` [PATCH v2 2/4] drivers: hwspinlock: add OMAP implementation Ohad Ben-Cohen
2010-11-23 23:23   ` Ionut Nicu
2010-11-24 10:33     ` Ohad Ben-Cohen
2010-11-23 15:38 ` [PATCH v2 3/4] OMAP4: hwmod data: Add hwspinlock Ohad Ben-Cohen
2010-11-23 15:39 ` [PATCH v2 4/4] omap: add hwspinlock device Ohad Ben-Cohen

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=20101130222328.GB17222@atomide.com \
    --to=tony@atomide.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=b-cousson@ti.com \
    --cc=grant.likely@secretlab.ca \
    --cc=greg@kroah.com \
    --cc=h-kanigeri2@ti.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=ohad@wizery.com \
    --cc=s-anna@ti.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