Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762445AbZAUBv3 (ORCPT ); Tue, 20 Jan 2009 20:51:29 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753339AbZAUBvS (ORCPT ); Tue, 20 Jan 2009 20:51:18 -0500 Received: from bombadil.infradead.org ([18.85.46.34]:55270 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761331AbZAUBvR (ORCPT ); Tue, 20 Jan 2009 20:51:17 -0500 Date: Tue, 20 Jan 2009 23:50:48 -0200 From: Mauro Carvalho Chehab To: Jaswinder Singh Rajput Cc: linux-media@vger.kernel.org, video4linux-list@redhat.com, Sam Ravnborg , Ingo Molnar , LKML Subject: Re: Confusion in usr/include/linux/videodev.h Message-ID: <20090120235048.4f7200f9@caramujo.chehab.org> In-Reply-To: <1232502038.3123.61.camel@localhost.localdomain> References: <1232502038.3123.61.camel@localhost.localdomain> X-Mailer: Claws Mail 3.3.1 (GTK+ 2.10.4; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1440 Lines: 34 On Wed, 21 Jan 2009 07:10:38 +0530 Jaswinder Singh Rajput wrote: > usr/include/linux/videodev.h is giving 2 warnings in 'make headers_check': > usr/include/linux/videodev.h:19: leaks CONFIG_VIDEO to userspace where it is not valid > usr/include/linux/videodev.h:314: leaks CONFIG_VIDEO to userspace where it is not valid > > Whole file is covered with #if defined(CONFIG_VIDEO_V4L1_COMPAT) || !defined (__KERNEL__) > > It means this file is only valid for kernel mode if CONFIG_VIDEO_V4L1_COMPAT is defined but in user mode it is always valid. > > Can we choose some better alternative Or can we use this file as: > > #ifdef CONFIG_VIDEO_V4L1_COMPAT > #include > #endif This is somewhat like what we have on audio devices (where there are OSS and ALSA API's). V4L1 is the old deprecated userspace API for video devices. It is still required by some userspace applications. So, on userspace, it should be included. Also, this allows that one userspace app to be compatible with both V4L2 API (the current one) and the legacy V4L1 one. It should be noticed that are still a few drivers using the legacy API yet to be converted. Cheers, Mauro -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/