public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jean Delvare <khali@linux-fr.org>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Hans de Goede <hdegoede@redhat.com>
Subject: Re: linux-next: build failure after merge of the final tree (jdelvare-hwmon tree related)
Date: Wed, 16 Mar 2011 09:16:44 -0700	[thread overview]
Message-ID: <20110316091644.d050115e.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20110315192428.ce74a177.sfr@canb.auug.org.au>

On Tue, 15 Mar 2011 19:24:28 +1100 Stephen Rothwell wrote:

> Hi all,
> 
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
> 
> drivers/hwmon/sch5627.c: In function 'sch5627_read_virtual_reg':
> drivers/hwmon/sch5627.c:179: error: implicit declaration of function 'msleep'
> 
> Caused by commit 19803daeb145 ("hwmon: New driver for SMSC SCH5627").
> See Rule 1 in Documentation/SubmitChecklist.
> 
> I have reverted that commit for today.


linux-next-20110316/drivers/i2c/busses/i2c-designware-core.c:321: error: implicit declaration of function 'mdelay'

linux-next-20110316/drivers/staging/altera-stapl/altera-jtag.c:398: error: implicit declaration of function 'udelay'

patch has been posted for altera-jtag.c, but not merged.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  parent reply	other threads:[~2011-03-16 16:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15  8:24 linux-next: build failure after merge of the final tree (jdelvare-hwmon tree related) Stephen Rothwell
2011-03-15  8:40 ` Hans de Goede
2011-03-15  9:32   ` Jean Delvare
2011-03-15 10:22     ` Stephen Rothwell
2011-03-16 11:30       ` Jean Delvare
2011-03-17 12:18       ` Geert Uytterhoeven
2011-03-17 15:36         ` Jean Delvare
2011-03-16 16:16 ` Randy Dunlap [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-10-06  4:28 Stephen Rothwell
2010-10-06  7:05 ` Jean Delvare

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=20110316091644.d050115e.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=hdegoede@redhat.com \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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