From: Olof Johansson <olof@lixom•net>
To: Milton Miller <miltonm@bga•com>
Cc: paulus@samba•org, linuxppc-dev@ozlabs•org
Subject: Re: [PATCH v2] powerpc: Add workaround for MPICs with broken register reads
Date: Fri, 7 Sep 2007 14:12:34 -0500 [thread overview]
Message-ID: <20070907191234.GA6851@lixom.net> (raw)
In-Reply-To: <326829233f0e99b0e0404241f5faaa7a@bga.com>
On Fri, Sep 07, 2007 at 09:11:52AM -0500, Milton Miller wrote:
> I'm sorry, I didn't mean to imply it should be asked / selectable, just
> that the help should be provided. I won't object to leaving it except
> that it asks the average user unnecessary questions. In other words, drop
> the question after bool.
Sigh. Why is it always that the simple patches/changes require 3 respins? It's
a valid point though, posting v3.
-Olof
next prev parent reply other threads:[~2007-09-07 19:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 2:44 [PATCH] powerpc: Add workaround for MPICs with broken register reads Olof Johansson
2007-09-06 14:55 ` Milton Miller
2007-09-07 9:16 ` Olof Johansson
2007-09-07 9:21 ` [PATCH v2] " Olof Johansson
2007-09-07 14:11 ` Milton Miller
2007-09-07 19:12 ` Olof Johansson [this message]
2007-09-07 19:13 ` [PATCH v3] " Olof Johansson
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=20070907191234.GA6851@lixom.net \
--to=olof@lixom$(echo .)net \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=miltonm@bga$(echo .)com \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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