From: Sam Ravnborg <sam@ravnborg.org>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: dri-devel@lists.freedesktop.org,
Maxime Ripard <maxime.ripard@bootlin.com>,
open list <linux-kernel@vger.kernel.org>,
David Airlie <airlied@linux.ie>,
tzimmermann@suse.de, Sean Paul <sean@poorly.run>
Subject: Re: [PATCH 1/3] drm: add gem ttm helpers
Date: Tue, 6 Aug 2019 17:46:27 +0200 [thread overview]
Message-ID: <20190806154627.GA10478@ravnborg.org> (raw)
In-Reply-To: <20190806133454.8254-2-kraxel@redhat.com>
Hi Gerd.
On Tue, Aug 06, 2019 at 03:34:52PM +0200, Gerd Hoffmann wrote:
> Now with ttm_buffer_object being a subclass of drm_gem_object we can
> easily lookup ttm_buffer_object for a given drm_gem_object, which in
> turm allows to create common helper functions. This patch starts off
> with dump mmap helpers.
>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
One nit below.
> ---
> include/drm/drm_gem_ttm_helper.h | 27 +++++++++++++++
> drivers/gpu/drm/drm_gem_ttm_helper.c | 52 ++++++++++++++++++++++++++++
> drivers/gpu/drm/Kconfig | 7 ++++
> drivers/gpu/drm/Makefile | 3 ++
> 4 files changed, 89 insertions(+)
> create mode 100644 include/drm/drm_gem_ttm_helper.h
> create mode 100644 drivers/gpu/drm/drm_gem_ttm_helper.c
>
> diff --git a/include/drm/drm_gem_ttm_helper.h b/include/drm/drm_gem_ttm_helper.h
> new file mode 100644
> index 000000000000..2c6874190b17
> --- /dev/null
> +++ b/include/drm/drm_gem_ttm_helper.h
> @@ -0,0 +1,27 @@
> +/* SPDX-License-Identifier: GPL-2.0-or-later */
> +
> +#ifndef DRM_GEM_TTM_HELPER_H
> +#define DRM_GEM_TTM_HELPER_H
> +
> +#include <drm/drm_gem.h>
> +#include <drm/ttm/ttm_bo_api.h>
> +#include <linux/kernel.h> /* for container_of() */
The typical order of include files is:
#include <linux/*>
#include <drm/*>
So space between each block of includes and sort within each block.
The comment "/* for container_of() */" is not really useful for
anyone.
Sam
next prev parent reply other threads:[~2019-08-06 15:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190806133454.8254-1-kraxel@redhat.com>
2019-08-06 13:34 ` [PATCH 1/3] drm: add gem ttm helpers Gerd Hoffmann
2019-08-06 13:54 ` Daniel Vetter
2019-08-07 7:26 ` Gerd Hoffmann
2019-08-07 8:28 ` Daniel Vetter
2019-08-07 10:36 ` Gerd Hoffmann
2019-08-07 11:40 ` Daniel Vetter
2019-08-07 11:51 ` Gerd Hoffmann
2019-08-07 21:08 ` Daniel Vetter
2019-08-06 15:46 ` Sam Ravnborg [this message]
2019-08-06 15:51 ` Sam Ravnborg
2019-08-06 13:34 ` [PATCH 2/3] drm/vram: switch vram helpers to use the new " Gerd Hoffmann
2019-08-06 13:34 ` [PATCH 3/3] drm/qxl: switch qxl " Gerd Hoffmann
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=20190806154627.GA10478@ravnborg.org \
--to=sam@ravnborg.org \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@bootlin.com \
--cc=sean@poorly.run \
--cc=tzimmermann@suse.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