From: Mark Brown <broonie@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Davide Ciminaghi <ciminaghi@gnudd.com>,
Stephen Warren <swarren@wwwdotorg.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] regmap: Make regmap-mmio usable from different contexts
Date: Thu, 23 May 2013 10:14:20 -0500 [thread overview]
Message-ID: <20130523151420.GA6406@sirena.org.uk> (raw)
In-Reply-To: <519E2985.8000704@metafoo.de>
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
On Thu, May 23, 2013 at 04:36:53PM +0200, Lars-Peter Clausen wrote:
> On 05/23/2013 04:31 PM, Mark Brown wrote:
> > So you'd have to allocate a struct on the stack with a pointer and the
> > flags in it and initialise the pointer. Not awesome but not the end of
> > the world.
> I'm not sure I understand what you mean. This needs to be done for each
> caller of a lock()/unlock() pair. We can't allocate the flags on the stack
> inside the lock() function since the stack will be gone once the function exits.
Allocate the struct on the stack - if you can allocate flags on the
stack you can allocate the struct on the stack too. Though I suppose
you still need to change all the callers for this which is just nasty
and makes it seem pointless to bother with abstraction here.
This is all stuff you should've been going through in the changelog when
you're jumping off into something that involves changing every single
user...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-05-23 15:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 13:06 [PATCH 1/2] regmap: regcache: Fixup locking for custom lock callbacks Lars-Peter Clausen
2013-05-23 13:06 ` [PATCH 2/2] regmap: Make regmap-mmio usable from different contexts Lars-Peter Clausen
2013-05-23 14:05 ` Mark Brown
2013-05-23 14:20 ` Lars-Peter Clausen
2013-05-23 14:31 ` Mark Brown
2013-05-23 14:36 ` Lars-Peter Clausen
2013-05-23 15:14 ` Mark Brown [this message]
2013-05-23 15:42 ` Stephen Warren
2013-05-23 15:50 ` Lars-Peter Clausen
2013-05-23 16:06 ` Stephen Warren
2013-05-23 16:10 ` Mark Brown
2013-05-23 16:01 ` Mark Brown
2013-05-23 14:08 ` [PATCH 1/2] regmap: regcache: Fixup locking for custom lock callbacks Mark Brown
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=20130523151420.GA6406@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ciminaghi@gnudd.com \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=swarren@wwwdotorg.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