From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: David Miller <davem@davemloft.net>,
akpm@linux-foundation.org, mbligh@google.com,
linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: [PATCH] Fix sparc TIF_USEDFPU flag atomicity
Date: Sat, 10 Mar 2007 11:31:09 -0500 [thread overview]
Message-ID: <20070310163109.GA5901@Krystal> (raw)
In-Reply-To: <20070310105903.GA8915@holomorphy.com>
* William Lee Irwin III (wli@holomorphy.com) wrote:
> On Sat, 10 Mar 2007 00:26:46 -0800, William Lee Irwin III <wli@holomorphy.com> wrote:
> >> Oh dear. Could we bit a bit more idiomatic here? For instance,
> >> something like:
>
> On Sat, Mar 10, 2007 at 12:29:44AM -0800, David Miller wrote:
> > Ok I pulled the sparc32 patch back out until there is some
> > consensus here :)
>
> It's just a minor touch-up. If Mathieu is okay with it, I'd rather
> leave him as the author and just send along an Acked-by: with it.
> I'm not terribly attached to it, either. I just choked on my soda
> when I saw set_ti_thread_flag(task_thread_info(fpt), TI_USEDFPU)
> etc. go by. (Which reminds me, I really need to figure out how to
> consolidate the UP and SMP cases for all this.)
>
>
> -- wli
Hello,
William's implementation is indeed neater than mine. So the consensus
goes to his patch as far as I'm concerned.
Mathieu
--
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next prev parent reply other threads:[~2007-03-10 16:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-10 8:17 [PATCH] Fix sparc TIF_USEDFPU flag atomicity Mathieu Desnoyers
2007-03-10 8:26 ` William Lee Irwin III
2007-03-10 8:29 ` David Miller
2007-03-10 10:59 ` William Lee Irwin III
2007-03-10 16:31 ` Mathieu Desnoyers [this message]
2007-03-10 8:28 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2007-03-09 3:12 Mathieu Desnoyers
2007-03-09 5:25 ` David Miller
2007-03-09 11:20 ` William Lee Irwin III
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=20070310163109.GA5901@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.com \
--cc=sparclinux@vger.kernel.org \
--cc=wli@holomorphy.com \
/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