linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: linux-next@vger.kernel.org
Subject: fix for "error: implicit declaration of function 'devres_alloc'" in Mar9 tree
Date: Fri, 9 Mar 2012 10:11:56 -0500	[thread overview]
Message-ID: <4F5A1DBC.3090701@windriver.com> (raw)

There are a couple builds showing:

drivers/base/regmap/regmap.c:331: error: implicit declaration of function 'devres_alloc'
drivers/base/regmap/regmap.c:338: error: implicit declaration of function 'devres_add'
drivers/base/regmap/regmap.c:340: error: implicit declaration of function 'devres_free'
drivers/base/regmap/regmap.c:421: error: implicit declaration of function 'dev_err'
make[4]: *** [drivers/base/regmap/regmap.o] Error 1

This is caused by commit 19694b5ea1d3 which just appeared in today's next
tree exposing another implicit device.h user.  Just a quick note that I'll
take care of it by adding regmap.c to the below commit.

Paul.

---

commit 6382876888313b6c9e2002247d9fa24f02835651
Author: Paul Gortmaker <paul.gortmaker@windriver.com>
Date:   Sun Jan 22 11:23:42 2012 -0500

    device.h: cleanup users outside of linux/include (C files)
    
    For files that are actively using linux/device.h, make sure
    that they call it out.  This will allow us to clean up some
    of the implicit uses of linux/device.h within include/*
    without introducing build regressions.

             reply	other threads:[~2012-03-09 15:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-09 15:11 Paul Gortmaker [this message]
2012-03-11 12:48 ` fix for "error: implicit declaration of function 'devres_alloc'" in Mar9 tree Mark Brown
2012-03-11 16:09   ` Paul Gortmaker
2012-03-11 19:32     ` Mark Brown

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=4F5A1DBC.3090701@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=linux-next@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 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).