linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: rob@landley.net
Cc: blauwirbel@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: Commit 085219f79cad broke Sparc-32 back in 2.6.28.
Date: Fri, 26 Mar 2010 20:37:45 -0700 (PDT)	[thread overview]
Message-ID: <20100326.203745.04177541.davem@davemloft.net> (raw)
In-Reply-To: <201003262235.48736.rob@landley.net>

From: Rob Landley <rob@landley.net>
Date: Fri, 26 Mar 2010 22:35:47 -0500

> What exactly was the problem with just saying "unsigned short" when you mean 
> an unsigned short?  The way x86 does, and arm?  (If these ever change, it 
> breaks binary compatability.  Not sure what these changes were trying to 
> accomplish...)

I was trying to use well defined types that described the
usage and the origin of the definition.

I'm happy to use "unsigned short" or whatever works better.
Please send a patch.

  reply	other threads:[~2010-03-27  3:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201002110520.07620.rob@landley.net>
     [not found] ` <f43fc5581002201359x50aff2b1ofc4f816762bda597@mail.gmail.com>
     [not found]   ` <201002201712.23628.rob@landley.net>
2010-02-21 16:25     ` Commit 085219f79cad broke Sparc-32 back in 2.6.28 Rob Landley
2010-02-21 23:57       ` David Miller
2010-02-22  0:28         ` Bartlomiej Zolnierkiewicz
2010-02-22  2:03           ` Rob Landley
2010-02-22  2:06       ` David Miller
2010-03-27  3:35         ` Rob Landley
2010-03-27  3:37           ` David Miller [this message]
2010-03-27  7:44             ` Rob Landley
2010-03-27 23:31               ` David Miller

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=20100326.203745.04177541.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=blauwirbel@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    /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;
as well as URLs for NNTP newsgroup(s).