From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Sven Luther <sven.luther@wanadoo.fr>
Cc: Johannes Stezenbach <js@convergence.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6.0-test9 ioctl compile warnings in userspace
Date: Wed, 3 Dec 2003 13:56:48 +0100 [thread overview]
Message-ID: <20031203125648.GC1947@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <20031202114350.GA25170@iliana>
On Tue, 2 December 2003 12:43:50 +0100, Sven Luther wrote:
> On Wed, Nov 12, 2003 at 05:37:50PM +0100, Johannes Stezenbach wrote:
> > Hi,
> >
> > the patch below fixes
> >
> > warning: signed and unsigned type in conditional expression
> >
> > when compiling userspace programs with a glibc built against
> > 2.6 kernel headers.
> >
> > This is a better version of my previous patch which aims
> > to fix all affected architectures.
>
> I am curious about this.
>
> This patch has been proposed since almost a month or more now, and
> clearly nobody seems to care about this, since it didn't make it in the
> 2.6.0-test11 tarball (don't know about more recent bk trees though) nor
> do the debian glibc maintainer judge the issue important enough to act
> on it (despite it breaking buildage of other packages).
>
> So, is there a reason why not to solve this problem this way, or a
> particular reason why __invalid_size_argument_for_IOC is still int and
> not unsigned int ?
It doesn't clearly fix a bug, afaics. Also, most kernel hackers don't
care too much about the signed/unsigned warnings, as they are 99%
noise.
Resend the patch after 2.6.0 has been released, I don't see any change
for it to go in before.
Jörn
--
People will accept your ideas much more readily if you tell them
that Benjamin Franklin said it first.
-- unknown
next prev parent reply other threads:[~2003-12-03 12:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 16:37 [PATCH] 2.6.0-test9 ioctl compile warnings in userspace Johannes Stezenbach
2003-12-02 11:43 ` Sven Luther
2003-12-03 12:56 ` Jörn Engel [this message]
2003-12-03 13:06 ` Sven Luther
2003-12-03 13:33 ` Jörn Engel
2003-12-03 14:09 ` Sven Luther
2003-12-03 14:34 ` Jörn Engel
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=20031203125648.GC1947@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=js@convergence.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sven.luther@wanadoo.fr \
/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).