From: Arjan van de Ven <arjanv@redhat.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Albert Cahalan <albert@users.sourceforge.net>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>,
george@galis.org
Subject: Re: SATA_SIL works with 2.6.7-bk8 seagate drive, but oops
Date: Sat, 26 Jun 2004 18:14:46 +0200 [thread overview]
Message-ID: <1088266485.2805.9.camel@laptop.fenrus.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0406260855080.14449@ppc970.osdl.org>
[-- Attachment #1: Type: text/plain, Size: 514 bytes --]
On Sat, 2004-06-26 at 18:00, Linus Torvalds wrote:
> On Sat, 26 Jun 2004, Arjan van de Ven wrote:
> >
> > well.... this value is *passed to userspace* via the AT_ attributes ....
> > glibc probably nicely exports this info via sysconf(). I guess/hope your
> > tools are now using that ?
>
> Even then, it's a bug in my opinion.
Agreed 100%. It gets kind of fun though if you have say 32 bit emulation
in a 64 bit kernel and the 64 bit environment has a different user HZ
than the 32 bit env....
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-06-26 16:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-26 12:37 SATA_SIL works with 2.6.7-bk8 seagate drive, but oops Albert Cahalan
2004-06-26 15:12 ` Arjan van de Ven
2004-06-26 16:00 ` Linus Torvalds
2004-06-26 16:14 ` Arjan van de Ven [this message]
2004-06-26 17:17 ` Albert Cahalan
2004-06-26 17:13 ` Albert Cahalan
2004-06-26 15:54 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2004-06-24 15:59 SATA_SIL fails with 2.6.7-bk6 seagate drive George Georgalis
2004-06-24 18:46 ` Ricky Beam
2004-06-25 21:34 ` SATA_SIL works with 2.6.7-bk8 seagate drive, but oops George Georgalis
2004-06-25 23:16 ` Linus Torvalds
2004-06-28 2:12 ` George Georgalis
2004-06-29 8:46 ` Sebastian Slota
2004-06-30 4:43 ` George Georgalis
2004-06-30 6:16 ` Jeff Garzik
2004-07-02 23:01 ` George Georgalis
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=1088266485.2805.9.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=albert@users.sourceforge.net \
--cc=george@galis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.