From: Rusty Russell <rusty@rustcorp.com.au>
To: Greg KH <greg@kroah.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
sfr@canb.auug.org.au, Andries.Brouwer@cwi.nl, akpm@digeo.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] struct loop_info64
Date: Sat, 19 Apr 2003 14:54:59 +1000 [thread overview]
Message-ID: <20030419052538.9EA962C0C7@lists.samba.org> (raw)
In-Reply-To: Your message of "Fri, 18 Apr 2003 11:06:30 MST." <20030418180630.GA7247@kroah.com>
In message <20030418180630.GA7247@kroah.com> you write:
> On Fri, Apr 18, 2003 at 10:55:21AM -0700, Linus Torvalds wrote:
> >
> > But we really should have a __ptr64 type too. There's just no sane way to
> > tell gcc about it without requireing casts, which is inconvenient (which
> > means that right now it you just have to use __u64 for pointers if you
> > want to be able to share the structure across 32/64-bit architectures).
>
> I think that's what Stephan and Rusty tried to do with the
> kernel_ulong_t typedef in include/linux/mod_devicetable.h.
>
> Maybe that typedef could be changed into the __ptr64 type? Stephan?
Stephen is away on holidays.
The kernel_ulong_t here is different. It's because (for good or bad)
that header contains longs and is shared with userspace. Fortunately,
it's only now shared with one very particular program, which is in the
kernel source tree, so kludgery is less harmful.
Hope that clarifies,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2003-04-19 5:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-18 13:04 Andries.Brouwer
2003-04-18 16:26 ` Linus Torvalds
2003-04-18 16:55 ` Greg KH
2003-04-18 17:55 ` Linus Torvalds
2003-04-18 18:06 ` Greg KH
2003-04-18 19:12 ` Kai Germaschewski
2003-04-19 4:54 ` Rusty Russell [this message]
2003-04-18 17:19 Andries.Brouwer
2003-04-18 17:50 ` Linus Torvalds
[not found] <759098236@toto.iv>
2003-04-23 0:43 ` Peter Chubb
2003-04-23 8:20 Andries.Brouwer
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=20030419052538.9EA962C0C7@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=Andries.Brouwer@cwi.nl \
--cc=akpm@digeo.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®