linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Vroon <tony@linx.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-media@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: [PATCH -next] v4l2-ctrls.c: needs to include slab.h
Date: Wed, 11 Aug 2010 19:45:42 +0100	[thread overview]
Message-ID: <1281552342.5092.9.camel@localhost> (raw)
In-Reply-To: <20100809105635.4208c7ac.randy.dunlap@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 937 bytes --]

On Mon, 2010-08-09 at 10:56 -0700, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
> v4l2-ctrls.c needs to include slab.h to prevent build errors:

This appears to have been missed. Running mainline git:
Linux amalthea 2.6.35-06998-g3d30701 #1 SMP Wed Aug 11 15:33:16 BST 2010
x86_64 Intel(R) Core(TM)2 Duo CPU T9400 @ 2.53GHz GenuineIntel GNU/Linux

Enabling Video 4 Linux results in the breakage promised by Randy:
> drivers/media/video/v4l2-ctrls.c:766: error: implicit declaration of function 'kzalloc'
> drivers/media/video/v4l2-ctrls.c:786: error: implicit declaration of function 'kfree'
> drivers/media/video/v4l2-ctrls.c:1528: error: implicit declaration of function 'kmalloc'

Please apply.

Regards,
-- 
Tony Vroon
UNIX systems administrator
London Internet Exchange Ltd, Trinity Court, Trinity Street,
Peterborough, PE1 1DA
Registered in England number 3137929
E-Mail: tony@linx.net

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2010-08-11 18:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-09  3:23 linux-next: Tree for August 9 Stephen Rothwell
2010-08-09 17:08 ` linux-next: Tree for August 9 (nfs) Randy Dunlap
     [not found]   ` <20100809100856.b03a9bc1.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2010-08-12 16:18     ` Randy Dunlap
     [not found]       ` <20100812091842.6a3b84b9.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2010-08-12 17:31         ` Trond Myklebust
2010-08-12 17:36           ` Randy Dunlap
     [not found]             ` <4C643136.5090808-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2010-08-17 21:23               ` Trond Myklebust
     [not found]                 ` <1282080208.12506.7.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-08-17 21:39                   ` Randy Dunlap
2010-08-09 17:55 ` [patch -NEXT] usb/gadget/webcam: fix Kconfig depends again Randy Dunlap
2010-08-10 12:16   ` Laurent Pinchart
2010-08-10 14:48     ` Randy Dunlap
     [not found]       ` <4C6166D9.60607-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2010-08-10 14:53         ` Laurent Pinchart
     [not found]           ` <201008101653.08358.laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
2010-08-17 18:03             ` Randy Dunlap
2010-08-09 17:56 ` [PATCH -next] v4l2-ctrls.c: needs to include slab.h Randy Dunlap
2010-08-11 18:45   ` Tony Vroon [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=1281552342.5092.9.camel@localhost \
    --to=tony@linx.net \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.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).