All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: stefani@seibold.net
Cc: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>,
	David Woodhouse <David.Woodhouse@intel.com>,
	Nicolas Pitre <nico@fluxnic.net>,
	Vasiliy Kulikov <segooon@gmail.com>,
	linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
	Tejun Heo <tj@kernel.org>,
	akpm@linux-foundation.org, Jiri Slaby <jslaby@suse.cz>,
	Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
Subject: Re: [PATCH] Change struct flchip_shared spinlock locking into mutex
Date: Tue, 3 Aug 2010 10:25:52 +0200	[thread overview]
Message-ID: <201008031025.52409.arnd@arndb.de> (raw)
In-Reply-To: <1280778048-6208-1-git-send-email-stefani@seibold.net>

On Monday 02 August 2010, stefani@seibold.net wrote:
> From: Stefani Seibold <stefani@seibold.net>
> 
> This patch prevent to schedule while atomic by changing the
> flchip_shared spinlock into a mutex. This should be save since no atomic
> path will use this lock.

I don't know this code well, but the patch looks correct and seems
to be needed.

Acked-by: Arnd Bergmann <arnd@arndb.de>

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: stefani@seibold.net
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	Vasiliy Kulikov <segooon@gmail.com>,
	Artem Bityutskiy <Artem.Bityutskiy@nokia.com>,
	David Woodhouse <David.Woodhouse@intel.com>,
	Nicolas Pitre <nico@fluxnic.net>,
	"Hans-Christian Egtvedt" <hans-christian.egtvedt@atmel.com>,
	Jiri Slaby <jslaby@suse.cz>, Tejun Heo <tj@kernel.org>,
	linux-mtd@lists.infradead.org
Subject: Re: [PATCH] Change struct flchip_shared spinlock locking into mutex
Date: Tue, 3 Aug 2010 10:25:52 +0200	[thread overview]
Message-ID: <201008031025.52409.arnd@arndb.de> (raw)
In-Reply-To: <1280778048-6208-1-git-send-email-stefani@seibold.net>

On Monday 02 August 2010, stefani@seibold.net wrote:
> From: Stefani Seibold <stefani@seibold.net>
> 
> This patch prevent to schedule while atomic by changing the
> flchip_shared spinlock into a mutex. This should be save since no atomic
> path will use this lock.

I don't know this code well, but the patch looks correct and seems
to be needed.

Acked-by: Arnd Bergmann <arnd@arndb.de>

  reply	other threads:[~2010-08-03  8:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-02 19:40 [PATCH] Change struct flchip_shared spinlock locking into mutex stefani
2010-08-03  8:25 ` Arnd Bergmann [this message]
2010-08-03  8:25   ` Arnd Bergmann
2010-08-05  4:58 ` Artem Bityutskiy
2010-08-05  4:58   ` Artem Bityutskiy
2010-08-05  5:30   ` Artem Bityutskiy
2010-08-05  5:30     ` Artem Bityutskiy
  -- strict thread matches above, loose matches on Subject: below --
2010-08-05  7:19 stefani
2010-08-05  9:37 ` Artem Bityutskiy
2010-08-05  9:37   ` Artem Bityutskiy

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=201008031025.52409.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=Artem.Bityutskiy@nokia.com \
    --cc=David.Woodhouse@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=hans-christian.egtvedt@atmel.com \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nico@fluxnic.net \
    --cc=segooon@gmail.com \
    --cc=stefani@seibold.net \
    --cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.