From: David Miller <davem@davemloft.net>
To: paul.gortmaker@windriver.com
Cc: rob.herring@calxeda.com, grant.likely@secretlab.ca,
sam@ravnborg.org, devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org,
linux-rt-users@vger.kernel.org, tglx@linutronix.de
Subject: Re: [PATCH next] OF: convert devtree lock from rw_lock to raw spinlock
Date: Mon, 04 Feb 2013 12:54:50 -0500 (EST) [thread overview]
Message-ID: <20130204.125450.2011131720910598109.davem@davemloft.net> (raw)
In-Reply-To: <1359993921-18145-1-git-send-email-paul.gortmaker@windriver.com>
From: Paul Gortmaker <paul.gortmaker@windriver.com>
Date: Mon, 4 Feb 2013 11:05:21 -0500
> From: Thomas Gleixner <tglx@linutronix.de>
>
> With the locking cleanup in place (from "OF: Fixup resursive
> locking code paths"), we can now do the conversion from the
> rw_lock to a raw spinlock as required for preempt-rt.
>
> The previous cleanup and the this conversion were originally
> separate since they predated when mainline got raw spinlock (in
> commit c2f21ce2e31286a "locking: Implement new raw_spinlock").
>
> So, at that point in time, the cleanup was considered plausible
> for mainline, but not this conversion. In any case, we've kept
> them separate as it makes for easier review and better bisection.
>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> [PG: taken from preempt-rt, update subject & add a commit log]
> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Acked-by: David S. Miller <davem@davemloft.net>
next prev parent reply other threads:[~2013-02-04 17:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 16:05 [PATCH next] OF: convert devtree lock from rw_lock to raw spinlock Paul Gortmaker
2013-02-04 17:54 ` David Miller [this message]
2013-02-06 16:04 ` Rob Herring
2013-02-06 20:30 ` [PATCH next v2] " Paul Gortmaker
2013-02-08 23:09 ` Rob Herring
[not found] ` <511585A9.9090008-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-02-11 19:29 ` Stephen Warren
2013-02-11 19:54 ` Rob Herring
2013-02-11 22:18 ` Grant Likely
2013-02-11 22:21 ` Rob Herring
2013-02-11 22:29 ` Grant Likely
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=20130204.125450.2011131720910598109.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=rob.herring@calxeda.com \
--cc=sam@ravnborg.org \
--cc=sparclinux@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).