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

On Fri, Apr 18, 2003 at 09:26:08AM -0700, Linus Torvalds wrote:
> 
> We should literally have the rule that any user-visible data structures 
> cannot use _any_ types other than u8/u16/u32/u64 (and _maybe_ the signed 
> ones, if there is any real reason to).

I thought we did have such a rule.  Well, it's unwritten I guess...
I'll go knock up a Documentation/user_to_kernel_datatypes.txt file to
set this in stone.

Oh, and shouldn't we be using the "__*" style types for crossing the
user/kernel boundry (__u8, __u16, __u32, etc.)?  I thought that is what
those versions were for.

thanks,

greg k-h

  reply	other threads:[~2003-04-18 16:41 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 [this message]
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
  -- 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=20030418165506.GA6834@kroah.com \
    --to=greg@kroah.com \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --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.