All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Warne <nick@linicks.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 3.12-rc2
Date: Tue, 24 Sep 2013 08:19:43 +0100	[thread overview]
Message-ID: <20130924071943.GA2112@sauron> (raw)
In-Reply-To: <20130920195939.GA2353@sauron>

Hi all,

I have couple of  build warnings.  Not sure if this happened with rc1, as I only have moved across to the rc trees:

gcc (GCC) 4.2.4 on amd64 - no modules build:


1)
...
  GEN     lib/crc32table.h
  CC      lib/crc32.o
lib/crc32.c: In function ‘crc32_be’:
lib/crc32.c:263: warning: passing argument 4 of ‘crc32_be_generic’ from incompatible pointer type
lib/crc32.c: In function ‘__crc32c_le’:
lib/crc32.c:199: warning: passing argument 4 of ‘crc32_le_generic’ from incompatible pointer type
lib/crc32.c: In function ‘crc32_le’:
lib/crc32.c:194: warning: passing argument 4 of ‘crc32_le_generic’ from incompatible pointer type
  CC      lib/fonts/fonts.o
...

2)
  CC      lib/radix-tree.o
lib/radix-tree.c: In function ‘radix_tree_next_chunk’:
lib/radix-tree.c:805: warning: comparison is always false due to limited range of data type
  CC      lib/ratelimit.o
...


Nick
-- 
http://linicks.net/

  parent reply	other threads:[~2013-09-24  7:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-20 19:59 [PATCH] Correct wording in config COMPILE_TEST Nick Warne
2013-09-22 10:40 ` Samsung laptop - missing documentation Nick Warne
2013-09-22 10:51   ` IGNORE_THIS " Nick Warne
2013-09-22 10:54   ` Borislav Petkov
2013-09-26 17:25   ` Samsung N145 Plus lid state issue on sleep Nick Warne
2013-09-28 21:14     ` Nick Warne
2013-10-03 17:07       ` Nick Warne
2013-09-24  7:19 ` Nick Warne [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-09-23 23:00 Linux 3.12-rc2 Linus Torvalds

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=20130924071943.GA2112@sauron \
    --to=nick@linicks.net \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.