public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	Randy Dunlap <rdunlap@xenotime.net>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>,
	Mikael Starvik <starvik@axis.com>,
	Jesper Nilsson <jesper.nilsson@axis.com>,
	linux-cris-kernel@axis.com
Subject: Re: Build regressions/improvements in v3.0-rc5 (ssize_t ???)
Date: Thu, 30 Jun 2011 19:07:08 +0200	[thread overview]
Message-ID: <m2y60jmeo3.fsf@igel.home> (raw)
In-Reply-To: <BANLkTik81kgf=g+QngnaB7gNUF+xCQdSvw@mail.gmail.com> (Geert Uytterhoeven's message of "Thu, 30 Jun 2011 10:43:47 +0200")

Geert Uytterhoeven <geert@linux-m68k.org> writes:

> On Thu, Jun 30, 2011 at 10:01, Christoph Hellwig <hch@infradead.org> wrote:
>> On Thu, Jun 30, 2011 at 08:59:28AM +0200, Geert Uytterhoeven wrote:
>>> Nope. Also only happens on cris, which has in
>>> arch/cris/include/asm/posix_types.h:
>>>
>>> typedef long            __kernel_ssize_t;
>>>
>>> The "long" should be "int".
>>> But probably it should just include <asm-generic/posix_types.h> instead.
>>
>> Changing a user visible type won't be very nice for those using it in
>> C++ code.
>
> Are __kernel_* types exported to C++ userspace?

Currently, no exported kernel header is using __kernel_ssize_t, so it
may not be too late to change cris.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  parent reply	other threads:[~2011-06-30 17:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-29  8:13 Build regressions/improvements in v3.0-rc5 Geert Uytterhoeven
2011-06-29 21:06 ` Build regressions/improvements in v3.0-rc5 (arch/cris) Randy Dunlap
2011-06-30  8:23   ` Américo Wang
2011-06-29 21:06 ` Build regressions/improvements in v3.0-rc5 (ssize_t ???) Randy Dunlap
2011-06-30  6:59   ` Geert Uytterhoeven
2011-06-30  7:16     ` Mikael Starvik
2011-06-30  8:01     ` Christoph Hellwig
2011-06-30  8:43       ` Geert Uytterhoeven
2011-06-30  8:56         ` Christoph Hellwig
2011-06-30  9:32           ` Geert Uytterhoeven
2011-06-30  9:44             ` Christoph Hellwig
2011-06-30 17:07         ` Andreas Schwab [this message]
2011-07-01  5:25           ` Mikael Starvik
2011-07-01  8:34             ` Andreas Schwab
2011-06-30 16:12     ` Randy Dunlap
2011-06-29 21:21 ` Build regressions/improvements in v3.0-rc5 (xfs on cris) Randy Dunlap
2011-06-29 21:24   ` Christoph Hellwig
2011-06-30  8:34     ` Américo Wang
2011-07-01 22:05 ` Build regressions/improvements in v3.0-rc5 Arnd Bergmann
2011-07-01 23:15   ` Mike Frysinger
2011-07-02  8:38     ` Arnd Bergmann

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=m2y60jmeo3.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=geert@linux-m68k.org \
    --cc=hch@infradead.org \
    --cc=jesper.nilsson@axis.com \
    --cc=linux-cris-kernel@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=starvik@axis.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