From: Matthew Wilcox <willy@debian.org>
To: linux-kernel@vger.kernel.org, rth@twiddle.net, spyro@f2s.com,
rmk@arm.linux.org.uk, davidm@hpl.hp.com, paulus@au.ibm.com,
benh@kernel.crashing.org, jes@trained-monkey.org, ralf@gnu.org,
matthew@wil.cx, davem@redhat.com, wesolows@foobazco.org,
jdike@karaya.com, ak@suse.de
Subject: Re: [PATCH] sort out CLOCK_TICK_RATE usage, 2nd try [0/3]
Date: Wed, 14 Apr 2004 15:12:45 +0100 [thread overview]
Message-ID: <20040414141245.GC18329@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20040413215833.A7047@Marvin.DL8BCU.ampr.org>
On Tue, Apr 13, 2004 at 09:58:33PM +0000, Thorsten Kranzkowski wrote:
> Arch maintainers please have a look whether I got the constants right or
> if your architecture has a PIC or speaker at all.
parisc certainly doesn't. i'd start by making this change for alpha,
x86 and x86_64 and make the PC speaker depend on (ALPHA || X86 || X86_64)
then other arches can take it from there if they want to supoprt the
pc speaker.
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
next prev parent reply other threads:[~2004-04-14 14:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-12 7:55 [PATCH][RFC] sort out CLOCK_TICK_RATE usage [0/3] Thorsten Kranzkowski
2004-04-12 7:57 ` [PATCH][RFC] sort out CLOCK_TICK_RATE usage [1/3] Thorsten Kranzkowski
2004-04-12 7:57 ` [PATCH][RFC] sort out CLOCK_TICK_RATE usage [2/3] Thorsten Kranzkowski
2004-04-12 7:58 ` [PATCH][RFC] sort out CLOCK_TICK_RATE usage [3/3] Thorsten Kranzkowski
2004-04-12 16:39 ` [PATCH][RFC] sort out CLOCK_TICK_RATE usage [1/3] David Mosberger
2004-04-12 20:08 ` Thorsten Kranzkowski
2004-04-12 20:32 ` David Mosberger
2004-04-12 21:17 ` Thorsten Kranzkowski
2004-04-13 4:04 ` Miles Bader
2004-04-13 17:00 ` Thorsten Kranzkowski
2004-04-14 1:45 ` Miles Bader
2004-04-12 16:47 ` [PATCH][RFC] sort out CLOCK_TICK_RATE usage [0/3] Zwane Mwaikambo
2004-04-12 20:11 ` Thorsten Kranzkowski
2004-04-12 20:50 ` Zwane Mwaikambo
2004-04-13 21:58 ` [PATCH] sort out CLOCK_TICK_RATE usage, 2nd try [0/3] Thorsten Kranzkowski
2004-04-13 21:59 ` [PATCH] sort out CLOCK_TICK_RATE usage, 2nd try [1/3] Thorsten Kranzkowski
2004-04-13 22:01 ` [PATCH] sort out CLOCK_TICK_RATE usage, 2nd try [2/3] Thorsten Kranzkowski
2004-04-13 22:02 ` [PATCH] sort out CLOCK_TICK_RATE usage, 2nd try [3/3] Thorsten Kranzkowski
2004-04-13 22:39 ` Randy.Dunlap
2004-04-14 14:12 ` Matthew Wilcox [this message]
2004-04-16 9:05 ` [PATCH] sort out CLOCK_TICK_RATE usage, 2nd try [0/3] Geert Uytterhoeven
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=20040414141245.GC18329@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=ak@suse.de \
--cc=benh@kernel.crashing.org \
--cc=davem@redhat.com \
--cc=davidm@hpl.hp.com \
--cc=jdike@karaya.com \
--cc=jes@trained-monkey.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=paulus@au.ibm.com \
--cc=ralf@gnu.org \
--cc=rmk@arm.linux.org.uk \
--cc=rth@twiddle.net \
--cc=spyro@f2s.com \
--cc=wesolows@foobazco.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®