From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Nicolas Pitre <nico@fluxnic.net>, Rabin Vincent <rabin@rab.in>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [PATCH] ARM: cache-v7: Disable preemption when reading CCSIDR
Date: Mon, 13 Feb 2012 23:29:01 +0000 [thread overview]
Message-ID: <20120213232901.GG25655@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4F398D61.9080501@codeaurora.org>
On Mon, Feb 13, 2012 at 02:23:29PM -0800, Stephen Boyd wrote:
> On 02/13/12 10:15, Russell King - ARM Linux wrote:
> > On Mon, Feb 13, 2012 at 10:13:27AM -0800, Stephen Boyd wrote:
> >> Thanks. Russell has already merged the original patch to the fixes
> >> branch. Hopefully he can fold this one in.
> > Nope, I've asked Linus to pull it.
> >
> > So do we conclude that the original patch wasn't properly tested? :P
>
> Sigh. Lockdep strikes again! I promise I tested it with lockdep disabled.
>
> It looks like Linus' hasn't pulled yet but maybe he just hasn't
> published it.
It's not nice to change something after you've sent a pull request -
there's no way of knowing when Linus actually pulls it before he's
published it, and if he gets something different then it can raise
questions.
So, it's gone in as-is, and, as I'm now intending asking for another
pull request soo soon after my previous one, this is something that
we will have to live with probably for the remainder of the week.
Note that you should, by default, build your development kernels with
lockdep enabled, it's there as a debugging tool to help you find
logical locking errors faster than people can provoke deadlocks.
next prev parent reply other threads:[~2012-02-13 23:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 19:24 Stephen Boyd
2012-02-02 20:44 ` Russell King - ARM Linux
2012-02-02 21:38 ` Nicolas Pitre
2012-02-02 23:36 ` Stephen Boyd
2012-02-03 0:36 ` Russell King - ARM Linux
2012-02-03 0:49 ` Stephen Boyd
2012-02-03 1:18 ` Nicolas Pitre
2012-02-03 2:03 ` Stephen Boyd
2012-02-03 2:35 ` Nicolas Pitre
2012-02-03 2:37 ` Stephen Boyd
2012-02-03 3:04 ` Nicolas Pitre
2012-02-03 11:15 ` Sergei Shtylyov
2012-02-04 18:00 ` Catalin Marinas
2012-02-13 17:54 ` Rabin Vincent
2012-02-13 18:09 ` Nicolas Pitre
2012-02-13 18:13 ` Stephen Boyd
2012-02-13 18:15 ` Russell King - ARM Linux
2012-02-13 22:23 ` Stephen Boyd
2012-02-13 23:29 ` Russell King - ARM Linux [this message]
2012-02-14 14:15 ` Rabin Vincent
2012-02-14 17:30 ` Nicolas Pitre
2012-02-14 18:07 ` Stephen Boyd
2012-02-03 1:16 ` Nicolas Pitre
2012-02-07 3:34 ` Saravana Kannan
2012-02-07 17:42 ` Stephen Boyd
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=20120213232901.GG25655@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=rabin@rab.in \
--cc=sboyd@codeaurora.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
all inboxes | Powered by JetHome®