Hi Luis,
On Friday 12 October 2012 16:49:31 Luis R. Rodriguez wrote:
From: "Luis R. Rodriguez" mcgrof@do-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@lists.freedesktop.org Cc: linux-kernel@vger.kernel.org Cc: devel@driverdev.osuosl.org Cc: backports@vger.kernel.org
Cc: Rob Clark rob@ti.com Cc: Arnd Bergmann arnd@arndb.de Cc: Dave Jones davej@redhat.com Cc: David Airlie airlied@linux.ie Cc: Ben Skeggs bskeggs@redhat.com Cc: Alan Cox alan@lxorguk.ukuu.org.uk Cc: David Howells dhowells@redhat.com Cc: Thomas Gleixner tglx@linutronix.de Cc: Daniel Vetter daniel.vetter@ffwll.ch Cc: Jesse Barnes jbarnes@virtuousgeek.org Cc: Alex Deucher alexander.deucher@amd.com Cc: Paul E. McKenney paulmck@linux.vnet.ibm.com Cc: Greg Kroah-Hartman gregkh@linuxfoundation.org Cc: Laurent Pinchart laurent.pinchart@ideasonboard.com Signed-off-by: Luis R. Rodriguez mcgrof@do-not-panic.com