mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bernd Petrovitsch <bernd@firmix.at>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Roman Zippel <zippel@linux-m68k.org>,
	kbuild-devel@lists.sourceforge.net,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Pointer cast warnings in scripts/
Date: Tue, 21 Jun 2005 15:14:13 +0200	[thread overview]
Message-ID: <1119359653.18845.55.camel@tara.firmix.at> (raw)
In-Reply-To: <42B80F40.8000609@drzeus.cx>

On Tue, 2005-06-21 at 14:59 +0200, Pierre Ossman wrote:
[...]
> It should only be a matter of reversing the patches for Solaris then.
> But that will of course bring back the warnings on that platform. I'd
> say we should stick with what the standard says. Unfortunatly I don't

The C-standard about "char", "signed char" and "unsigned char"?
These are 3 different types.

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services


  reply	other threads:[~2005-06-21 13:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-21 11:17 Pierre Ossman
2005-06-21 12:06 ` Mikael Pettersson
2005-06-21 12:18 ` Roman Zippel
2005-06-21 12:41   ` Pierre Ossman
2005-06-21 12:51     ` Roman Zippel
2005-06-21 12:59       ` Pierre Ossman
2005-06-21 13:14         ` Bernd Petrovitsch [this message]
2005-06-22  9:21           ` Pierre Ossman
2005-06-22 10:04             ` Bernd Petrovitsch
2005-06-22 11:12               ` Pierre Ossman
2005-06-22 11:25                 ` Russell King
2005-06-21 13:20         ` Roman Zippel
2005-06-21 14:06           ` Pierre Ossman
2005-06-21 14:14             ` Roman Zippel
2005-06-21 21:31               ` J.A. Magallon
2005-06-21 14:19           ` J.A. Magallon
2005-06-21 13:25     ` Andreas Schwab

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=1119359653.18845.55.camel@tara.firmix.at \
    --to=bernd@firmix.at \
    --cc=drzeus-list@drzeus.cx \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zippel@linux-m68k.org \
    /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®