From: Peter Zijlstra <peterz@infradead.org>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
sparclinux@vger.kernel.org
Subject: Re: [PATCH 0/4]: Respin local_irq_*_nmi() stuff.
Date: Tue, 13 Apr 2010 09:48:58 +0200 [thread overview]
Message-ID: <1271144938.4807.925.camel@twins> (raw)
In-Reply-To: <20100412.220838.132238558.davem@davemloft.net>
On Mon, 2010-04-12 at 22:08 -0700, David Miller wrote:
> I'm rescinding these patches for now, for two reasons:
>
> 1) The NMI annotations necessary to get everything working really gets
> out of control.
>
> 2) I think I found a cheap way to do this in sparc64 specific code.
Ah, ok..
Care to enlighten the curious amongst us as to what exactly you're doing
in the sparc code?
next prev parent reply other threads:[~2010-04-13 7:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 23:01 [PATCH 0/4]: Respin local_irq_*_nmi() stuff David Miller
2010-04-09 23:01 ` David Miller
2010-04-13 5:08 ` David Miller
2010-04-13 7:48 ` Peter Zijlstra [this message]
2010-04-13 7:56 ` David Miller
2010-04-13 8:37 ` Peter Zijlstra
2010-04-13 8:37 ` Peter Zijlstra
2010-04-13 8:46 ` David Miller
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=1271144938.4807.925.camel@twins \
--to=peterz@infradead.org \
--cc=davem@davemloft.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.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 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).