Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jim Freeman <jfree@sovereign.org>
To: linux-mips@oss.sgi.com
Subject: hz_to_std(): parisc, etc.
Date: Fri, 2 Feb 2001 04:37:56 -0700	[thread overview]
Message-ID: <20010202043756.A3687@sovereign.org> (raw)

asm-parisc/param.h is missing the hz_to_std() macro that the
other asm-*/param.h have.

For the other missing asm-arm/arch-*, something like the following
could catch laggards?  Or the test could be used in linux/param.h,
though I expect Linus wouldn't like crufting the toplevel .h
for a mips-ism (or is hz_to_std() a needed non-mips-centric
general mechanism)?

--- linux-mips.cvs/include/asm-arm/param.h	2001/02/02 11:14:40	1.1
+++ linux-mips.cvs/include/asm-arm/param.h	2001/02/02 11:27:18
@@ -16,9 +16,14 @@
 #ifndef HZ
 #define HZ 100
 #endif
-#if defined(__KERNEL__) && (HZ == 100)
+#ifdef __KERNEL__
+#if (HZ == 100)
 #define hz_to_std(a) (a)
-#endif
+#endif /* (HZ == 100) */
+#if !defined(hz_to_std)
+#error hz_to_std not defined	/* see asm-arm/arch-shark/param.h for details */
+#endif /* !defined(hz_to_std) */
+#endif /* def __KERNEL__ */
 
 #ifndef NGROUPS
 #define NGROUPS         32
--- linux-mips.cvs/include/asm-arm/arch-shark/param.h	2001/02/02 11:16:59	1.1
+++ linux-mips.cvs/include/asm-arm/arch-shark/param.h	2001/02/02 11:19:24
@@ -15,7 +15,7 @@
 
    is what has to be done, it just has overflow problems with the
    intermediate result of the multiply after a bit more than 7 days.
-   See include/asm-mips/param.h for a optized sample implementation
+   See include/asm-mips/param.h for an optimized sample implementation
    used on DECstations.
  */
 #error Provide a definiton for hz_to_std

                 reply	other threads:[~2001-02-02 11:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20010202043756.A3687@sovereign.org \
    --to=jfree@sovereign.org \
    --cc=linux-mips@oss.sgi.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