LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Oleg Verych <olecom@flower.upol.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: warrning fix: unsigned->signed
Date: Tue, 6 Feb 2007 22:55:27 +0000 (UTC)	[thread overview]
Message-ID: <slrnesi2c0.90j.olecom@flower.upol.cz> (raw)
In-Reply-To: <20070206140936.24bbaded.akpm@linux-foundation.org>

> From: Andrew Morton
> Newsgroups: gmane.linux.kernel
> Subject: Re: [PATCH]: warrning fix: unsigned->signed
> Date: Tue, 6 Feb 2007 14:09:36 -0800
  Mail-Followup-To: LKML <linux-kernel@vger.kernel.org>, Oleg Verych <olecom@flower.upol.cz>, Andrew Morton <akpm@linux-foundation.org>, "Tomasz Kvarsin" <kvarsin@gmail.com>, viro@zeniv.linux.org.uk, axboe@kernel.dk

> On Wed, 7 Feb 2007 00:39:45 +0300
> "Tomasz Kvarsin" <kvarsin@gmail.com> wrote:
>
>> While compiling my code, I always get bunch of warrning from headers,
>> here is fix for them:
>> __getblk is alawys called with unsigned argument,
>> but it takes signed, the same story with __bread,__breadahead and so on.
>
> The patch seems OK, but I'm curious to know why you're seeing this warning
> and nobody else is.  Are you using a compiler other than gcc?  If gcc,
> which version?  Did you add any new compiler options?

Andrew, i think it's due to 

,-*- quote -*-
| Friends don't let friends use "-W". [0]
`-*-

I get many of them, when compiling external modules with `-Wall', of
course ;)

[0] Message-Id: Pine.LNX.4.64.0611281459331.4244@woody.osdl.org
    Archived-At: <http://permalink.gmane.org/gmane.linux.kernel/470736>

____


  reply	other threads:[~2007-02-06 22:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-06 21:39 Tomasz Kvarsin
2007-02-06 22:09 ` Andrew Morton
2007-02-06 22:55   ` Oleg Verych [this message]
2007-02-07  5:31   ` Tomasz Kvarsin
2007-02-07 11:56   ` Jens Axboe

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=slrnesi2c0.90j.olecom@flower.upol.cz \
    --to=olecom@flower.upol.cz \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [PATCH]: warrning fix: unsigned->signed' \
    /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

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).