From: Chuck Ebbert <76306.1226@compuserve.com>
To: Andi Kleen <ak@suse.de>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] i386: port ATI timer fix from x86_64 to i386
Date: Wed, 1 Mar 2006 12:10:27 -0500 [thread overview]
Message-ID: <200603011213_MC3-1-B998-965E@compuserve.com> (raw)
In-Reply-To: <p73psl6zbwf.fsf@verdi.suse.de>
On 01 Mar 2006 11:40:00, Andi Kleen wrote:
> > Wonderful, thanks. What's the relationship (if any) between this and the
> > recently-merged x86_64 fix?
>
> He just ported the x86-64 change over without any original authorship
> attribution :/
Oops, sorry about that. Since I wrote "ported from x86_64" I assumed
credit was implicit.
> And some less functionality (only works for ACPI now)
I documented that. Without ACPI there wasn't infrastructure to do the early
PCI scan.
> and some totally unrelated Documentation cleanup
I added the two new boot options. While doing that I noticed the *timer_pin_1
docs weren't in alphabetical order so I moved them.
> and a few random printk changes
One printk change. The other was an exact port of the message from x86_64.
And the change I made wasn't random. It might have been a bad idea but
it wasn't random.
--
Chuck
"The sleet in Crete falls neatly in the street."
next reply other threads:[~2006-03-01 17:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 17:10 Chuck Ebbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-01 15:50 Chuck Ebbert
2006-03-01 2:22 Chuck Ebbert
2006-03-01 1:18 Parag Warudkar
2006-03-01 0:03 Chuck Ebbert
2006-03-01 0:15 ` Andrew Morton
2006-03-01 10:40 ` Andi Kleen
2006-03-01 10:52 ` Andrew Morton
2006-03-01 11:07 ` Andi Kleen
2006-02-28 21:17 Chuck Ebbert
2006-02-28 23:21 ` Andrew Morton
2006-03-01 13:59 ` Alistair John Strachan
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=200603011213_MC3-1-B998-965E@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®