public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb•de>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Mark Brown <broonie@opensource•wolfsonmicro.com>,
	Liam Girdwood <lrg@ti•com>,
	linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (regulator tree related)
Date: Thu, 16 Aug 2012 06:39:46 +0000	[thread overview]
Message-ID: <201208160639.47131.arnd@arndb.de> (raw)
In-Reply-To: <20120816151605.b0a9932005b541956288ce96@canb.auug.org.au>

On Thursday 16 August 2012, Stephen Rothwell wrote:
> From: Stephen Rothwell <sfr@canb•auug.org.au>
> Date: Thu, 16 Aug 2012 15:11:22 +1000
> Subject: [PATCH] regulator: using kfree() requires including slab.h
> 
> Fixes this build error:
> 
> drivers/regulator/twl-regulator.c: In function 'twlreg_probe':
> drivers/regulator/twl-regulator.c:1229:3: error: implicit declaration of
> function 'kfree' [-Werror=implicit-function-declaration]
> 
> Also added string.h for kmemdup().
> 
> Signed-off-by: Stephen Rothwell <sfr@canb•auug.org.au>

Acked-by: Arnd Bergmann <arnd@arndb•de>

Thanks Stephen and sorry for bothering everyone with this. I had
actually found the same problem and fixed it locally but forgot
to send out the fixed version.

	Arnd

  reply	other threads:[~2012-08-16  6:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-16  5:16 linux-next: build failure after merge of the final tree (regulator tree related) Stephen Rothwell
2012-08-16  6:39 ` Arnd Bergmann [this message]
2012-08-16 10:58 ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2012-04-17  4:27 Stephen Rothwell
2012-04-17 13:55 ` Mark Brown
2012-04-16  5:52 Stephen Rothwell
2012-02-03  5:15 Stephen Rothwell
2012-02-03 11:02 ` 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=201208160639.47131.arnd@arndb.de \
    --to=arnd@arndb$(echo .)de \
    --cc=broonie@opensource$(echo .)wolfsonmicro.com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=lrg@ti$(echo .)com \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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