linux-kernel - Re: [PATCH 1/2] uapi: update includes for drm content when no kernel API exists

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 13 Oct 2012 12:33:32 +0200
From:	Laurent Pinchart <laurent.pinchart@...asonboard.com>
To:	"Luis R. Rodriguez" <mcgrof@...not-panic.com>
Cc:	dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
	devel@...verdev.osuosl.org, backports@...r.kernel.org, rob@...com,
	arnd@...db.de, davej@...hat.com, airlied@...ux.ie,
	bskeggs@...hat.com, alan@...rguk.ukuu.org.uk, dhowells@...hat.com,
	tglx@...utronix.de, daniel.vetter@...ll.ch,
	jbarnes@...tuousgeek.org, alexander.deucher@....com,
	paulmck@...ux.vnet.ibm.com, gregkh@...uxfoundation.org
Subject: Re: [PATCH 1/2] uapi: update includes for drm content when no kernel API exists

Hi Luis,

On Friday 12 October 2012 16:49:31 Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez" <mcgrof@...not-panic.com>
> 
> The UAPI changes split kernel API and userspace API
> content onto two separate header files. The userspace
> API drm content was moved to include/uapi/drm/ with the
> same file name while kernel specific API content was
> kept under include/drm/ with the same file name. When
> one file was split into two files the kernel header
> includes the uapi header and a UAPI prefix was added to
> the uapi header for its header guard. When there was no
> kernel API content found the uapi header file was the
> only one that was kept and the original guard for the
> header file was kept. In this particular case the
> original users of this header file were not modified
> and the uapi header file is expected to be picked up
> by path.
> 
> This may work well at compilation on the kernel but when
> backporting this creates a few complexities.

Could you please provide more details about those complexities ?

> To help with
> backporting [0] lets be explicit about the new uapi path
> when there is no respective kernel API header file. For
> more details on the UAPI changes see the lwn article on
> this [1].
> 
> [0] https://backports.wiki.kernel.org
> [1] http://lwn.net/Articles/507794/
> 
> Cc: dri-devel@...ts.freedesktop.org
> Cc: linux-kernel@...r.kernel.org
> Cc: devel@...verdev.osuosl.org
> Cc: backports@...r.kernel.org
> 
> Cc: Rob Clark <rob@...com>
> Cc: Arnd Bergmann <arnd@...db.de>
> Cc: Dave Jones <davej@...hat.com>
> Cc: David Airlie <airlied@...ux.ie>
> Cc: Ben Skeggs <bskeggs@...hat.com>
> Cc: Alan Cox <alan@...rguk.ukuu.org.uk>
> Cc: David Howells <dhowells@...hat.com>
> Cc: Thomas Gleixner <tglx@...utronix.de>
> Cc: Daniel Vetter <daniel.vetter@...ll.ch>
> Cc: Jesse Barnes <jbarnes@...tuousgeek.org>
> Cc: Alex Deucher <alexander.deucher@....com>
> Cc: Paul E. McKenney <paulmck@...ux.vnet.ibm.com>
> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> Cc: Laurent Pinchart <laurent.pinchart@...asonboard.com>
> Signed-off-by: Luis R. Rodriguez <mcgrof@...not-panic.com>

-- 
Regards,

Laurent Pinchart

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/