From: Ralf Baechle <ralf@linux-mips.org>
To: Bradley Bozarth <bbozarth@cisco.com>
Cc: linux-mips@linux-mips.org
Subject: Re: 64 bit jiffies
Date: Wed, 23 Oct 2002 16:26:52 +0200 [thread overview]
Message-ID: <20021023162652.A27187@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0210222038460.31553-100000@bbozarth-lnx.cisco.com>; from bbozarth@cisco.com on Tue, Oct 22, 2002 at 08:42:35PM -0700
On Tue, Oct 22, 2002 at 08:42:35PM -0700, Bradley Bozarth wrote:
> There was a thread on lkml in May which resulted in the 32 bit jiffies
> value using the bottom of the jiffies_64 - this equivalence being done in
> linker scripts. It was stated, however, that MIPS wasn't handled because
> it had a funky sed generated linker script for multiple endiannesses.
> So is mips currently broken in 2.5? Has anyone looked at this - I would
> be willing to figure out a fix but thought I'd see if someone has ideas or
> has already dealt with it...
This is long fixed in the 2.5 branch of CVS.
Ralf
prev parent reply other threads:[~2002-10-23 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 3:42 64 bit jiffies Bradley Bozarth
2002-10-23 14:26 ` Ralf Baechle [this message]
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=20021023162652.A27187@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=bbozarth@cisco.com \
--cc=linux-mips@linux-mips.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