From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Hugh Dickins <hughd@google.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: next BUG: using smp_processor_id() in preemptible
Date: Wed, 01 Feb 2012 21:48:40 +1100 [thread overview]
Message-ID: <1328093320.28487.75.camel@pasglop> (raw)
In-Reply-To: <alpine.LSU.2.00.1201312208270.1859@eggly.anvils>
On Tue, 2012-01-31 at 22:12 -0800, Hugh Dickins wrote:
> > Grrr, my memory is a colander... And now am in Ballarat for the week
> > with a semi working 3g connection. I'll see what I can do.
>
> Sorry to be such a bore - you can guess what I have to say about
> 3.3-rc2 :()
Yeah, I'm looking at reworking the whole thing, I think we have another
deeper problem with lazy interrupt disable and implicit re-enable from
an exception exit too... stay tuned.
Cheers,
Ben.
prev parent reply other threads:[~2012-02-01 10:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 23:51 next BUG: using smp_processor_id() in preemptible Hugh Dickins
2011-12-22 12:07 ` Hugh Dickins
2011-12-22 21:17 ` Benjamin Herrenschmidt
2012-01-14 22:21 ` Hugh Dickins
2012-01-15 5:05 ` Benjamin Herrenschmidt
2012-02-01 6:12 ` Hugh Dickins
2012-02-01 10:48 ` Benjamin Herrenschmidt [this message]
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=1328093320.28487.75.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=hughd@google.com \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).