From: Jani Nikula <jani.nikula@linux.intel.com>
To: dri-devel@lists.freedesktop.org
Cc: Maxime Ripard <maxime.ripard@bootlin.com>,
David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH v2 1/7] drm: make drm/drm_auth.h self contained
Date: Tue, 28 May 2019 15:54:48 +0300 [thread overview]
Message-ID: <87d0k268o7.fsf@intel.com> (raw)
In-Reply-To: <20190526173535.32701-2-sam@ravnborg.org>
On Sun, 26 May 2019, Sam Ravnborg <sam@ravnborg.org> wrote:
> Do not require users of include/drm/drm_auth.h to include
> other files just to let it build.
>
> Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Cc: Maxime Ripard <maxime.ripard@bootlin.com>
> Cc: Sean Paul <sean@poorly.run>
> Cc: David Airlie <airlied@linux.ie>
> Cc: Daniel Vetter <daniel@ffwll.ch>
> ---
> include/drm/drm_auth.h | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/include/drm/drm_auth.h b/include/drm/drm_auth.h
> index 871008118bab..6bf8b2b78991 100644
> --- a/include/drm/drm_auth.h
> +++ b/include/drm/drm_auth.h
> @@ -1,3 +1,6 @@
> +#ifndef _DRM_AUTH_H_
> +#define _DRM_AUTH_H_
> +
It's a bit of a bikeshed and this got applied already, but I think the
copyright/license comment should be the first thing in any file, and the
ifdefs should come after that. Using SPDX headers mandate this anyway.
BR,
Jani.
> /*
> * Internal Header for the Direct Rendering Manager
> *
> @@ -25,8 +28,12 @@
> * OTHER DEALINGS IN THE SOFTWARE.
> */
>
> -#ifndef _DRM_AUTH_H_
> -#define _DRM_AUTH_H_
> +#include <linux/idr.h>
> +#include <linux/kref.h>
> +#include <linux/wait.h>
> +
> +struct drm_file;
> +struct drm_hw_lock;
>
> /*
> * Legacy DRI1 locking data structure. Only here instead of in drm_legacy.h for
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-05-28 12:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-26 17:35 [PATCH v2 0/7] drm: make headers self-contained and drop drmP.h Sam Ravnborg
2019-05-26 17:35 ` [PATCH v2 1/7] drm: make drm/drm_auth.h self contained Sam Ravnborg
2019-05-28 12:54 ` Jani Nikula [this message]
2019-05-28 13:07 ` Sam Ravnborg
2019-05-26 17:35 ` [PATCH v2 2/7] drm: make drm/drm_legacy.h self-contained Sam Ravnborg
2019-05-26 17:35 ` [PATCH v2 3/7] drm: make drm_crtc_internal.h self-contained Sam Ravnborg
2019-05-26 17:35 ` [PATCH v2 4/7] drm: make drm_internal.h self-contained Sam Ravnborg
2019-05-26 17:35 ` [PATCH v2 5/7] drm: make drm_legacy.h self-contained Sam Ravnborg
2019-05-26 17:35 ` [PATCH v2 6/7] drm: make drm_trace.h self-contained Sam Ravnborg
2019-05-26 17:35 ` [PATCH v2 7/7] drm: drop use of drmP.h in drm/* Sam Ravnborg
2019-05-26 18:05 ` ✗ Fi.CI.CHECKPATCH: warning for drm: make headers self-contained and drop drmP.h Patchwork
2019-05-26 18:08 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-05-26 18:25 ` ✓ Fi.CI.BAT: success " Patchwork
2019-05-27 6:18 ` [PATCH v2 0/7] " Daniel Vetter
2019-05-27 6:54 ` Sam Ravnborg
2019-05-27 18:05 ` Sam Ravnborg
2019-05-27 12:00 ` ✓ Fi.CI.IGT: success for " Patchwork
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=87d0k268o7.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maxime.ripard@bootlin.com \
--cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.