All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Linus Torvalds <torvalds@transmeta.com>,
	sfr@canb.auug.org.au, rusty@rustcorp.com.au
Cc: Andries.Brouwer@cwi.nl, akpm@digeo.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] struct loop_info64
Date: Fri, 18 Apr 2003 11:06:30 -0700	[thread overview]
Message-ID: <20030418180630.GA7247@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0304181050430.2950-100000@home.transmeta.com>

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?

thanks,

greg k-h

  reply	other threads:[~2003-04-18 17:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-18 13:04 [PATCH] struct loop_info64 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 [this message]
2003-04-18 19:12         ` Kai Germaschewski
2003-04-19  4:54         ` Rusty Russell
  -- strict thread matches above, loose matches on Subject: below --
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=20030418180630.GA7247@kroah.com \
    --to=greg@kroah.com \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --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 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.