public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	devel@driverdev.osuosl.org, backports@vger.kernel.org,
	rob@ti.com, arnd@arndb.de, davej@redhat.com, airlied@linux.ie,
	bskeggs@redhat.com, alan@lxorguk.ukuu.org.uk,
	dhowells@redhat.com, tglx@linutronix.de, daniel.vetter@ffwll.ch,
	jbarnes@virtuousgeek.org, alexander.deucher@amd.com,
	paulmck@linux.vnet.ibm.com, gregkh@linuxfoundation.org
Subject: Re: [PATCH 1/2] uapi: update includes for drm content when no kernel API exists
Date: Sat, 13 Oct 2012 12:33:32 +0200	[thread overview]
Message-ID: <3084988.3Xup6S3alX@avalon> (raw)
In-Reply-To: <1350085772-8755-2-git-send-email-mcgrof@do-not-panic.com>

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>

-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2012-10-13 10:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-12 23:49 [PATCH 0/2] uapi: two minor changes Luis R. Rodriguez
2012-10-12 23:49 ` [PATCH 1/2] uapi: update includes for drm content when no kernel API exists Luis R. Rodriguez
2012-10-13 10:33   ` Laurent Pinchart [this message]
2012-10-13 17:00     ` Luis R. Rodriguez
2012-10-16 12:34       ` Laurent Pinchart
2012-10-16 14:38         ` Luis R. Rodriguez
2012-10-16 23:27           ` David Howells
2012-10-12 23:49 ` [PATCH 2/2] uapi: remove trailing spaces Luis R. Rodriguez

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=3084988.3Xup6S3alX@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=airlied@linux.ie \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=alexander.deucher@amd.com \
    --cc=arnd@arndb.de \
    --cc=backports@vger.kernel.org \
    --cc=bskeggs@redhat.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=davej@redhat.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=dhowells@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@do-not-panic.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=rob@ti.com \
    --cc=tglx@linutronix.de \
    /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