mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: linux-kernel@vger.kernel.org, wim@iguana.be
Subject: Re: build issue #552 for v2.6.27-rc2-325-g796aade :drivers/watchdog/pcwd.c : incompatible pointer type
Date: Sat, 9 Aug 2008 15:04:10 -0700	[thread overview]
Message-ID: <20080809150410.513c41ef.randy.dunlap@oracle.com> (raw)
In-Reply-To: <200808092154.11834.toralf.foerster@gmx.de>

On Sat, 9 Aug 2008 21:54:05 +0200 Toralf Förster wrote:

> Hello,
> 
> the build (.config attached) failed, make ends with :
> ...
>   CC      drivers/w1/slaves/w1_ds2433.o
>   CC      drivers/w1/slaves/w1_ds2760.o
>   LD      drivers/w1/slaves/built-in.o
>   LD      drivers/w1/built-in.o
>   CC      drivers/watchdog/pcwd.o
> drivers/watchdog/pcwd.c: In function 'pcwd_open':
> drivers/watchdog/pcwd.c:703: warning: passing argument 2 of 'test_and_set_bit' from incompatible pointer type
> drivers/watchdog/pcwd.c: In function 'pcwd_close':
> drivers/watchdog/pcwd.c:723: warning: passing argument 2 of 'clear_bit' from incompatible pointer type
>   CC      drivers/watchdog/mixcomwd.o
>   CC      drivers/watchdog/pcwd_pci.o
>   CC      drivers/watchdog/wdt_pci.o
>   CC      drivers/watchdog/acquirewdt.o
>   CC      drivers/watchdog/advantechwdt.o
>   CC      drivers/watchdog/alim7101_wdt.o
> drivers/watchdog/alim7101_wdt.c:424: warning: 'alim7101_pci_tbl' defined but not used
>   CC      drivers/watchdog/ibmasr.o
>   CC      drivers/watchdog/iTCO_wdt.o
>   CC      drivers/watchdog/iTCO_vendor_support.o
> drivers/watchdog/iTCO_vendor_support.c:247: error: expected identifier or '(' before '{' token
> drivers/watchdog/iTCO_vendor_support.c:249: error: expected identifier or '(' before '{' token
> drivers/watchdog/iTCO_vendor_support.c:257: error: expected identifier or '(' before '{' token
> drivers/watchdog/iTCO_vendor_support.c:258: error: expected identifier or '(' before '{' token
> drivers/watchdog/iTCO_vendor_support.c:266: error: expected identifier or '(' before '{' token
> drivers/watchdog/iTCO_vendor_support.c:267: error: expected identifier or '(' before '{' token
> drivers/watchdog/iTCO_vendor_support.c:275: error: expected identifier or '(' before '{' token
> drivers/watchdog/iTCO_vendor_support.c:276: error: expected identifier or '(' before '{' token
> drivers/watchdog/iTCO_vendor_support.c:282:39: error: macro "iTCO_vendor_check_noreboot_on" passed 1 arguments, but takes just 0
> drivers/watchdog/iTCO_vendor_support.c:283: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
> make[2]: *** [drivers/watchdog/iTCO_vendor_support.o] Error 1
> make[1]: *** [drivers/watchdog] Error 2
> make: *** [drivers] Error 2
> 
> The build was made with :
> $>make randconfig; make clean; make
> 
> Here's the config:

Looks the same as reported on 8/8 with patch:
http://marc.info/?l=linux-kernel&m=121818422630481&w=2

---
~Randy
Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA
http://linuxplumbersconf.org/

      reply	other threads:[~2008-08-09 22:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-09 19:54 Toralf Förster
2008-08-09 22:04 ` Randy Dunlap [this message]

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=20080809150410.513c41ef.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=toralf.foerster@gmx.de \
    --cc=wim@iguana.be \
    /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®