From: Jani Nikula <jani.nikula@linux.intel.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>,
David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org
Cc: "Christian K\?nig" <christian.koenig@amd.com>,
Alexander Deucher <Alexander.Deucher@amd.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Daniel Vetter <daniel.vetter@intel.com>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 5/5] drm/i915: use i915_gem_open() directly instead of i915_driver_open()
Date: Thu, 15 Sep 2016 12:46:17 +0300 [thread overview]
Message-ID: <87twdhpkba.fsf@intel.com> (raw)
In-Reply-To: <1473863952-7658-6-git-send-email-yamada.masahiro@socionext.com>
On Wed, 14 Sep 2016, Masahiro Yamada <yamada.masahiro@socionext.com> wrote:
> i915_driver_open() is equivalent to i915_gem_open(). Replace the
> i915_driver_open with the direct use of i915_gem_open().
Sorry I know I asked for this, but there was opposition to doing
this. Please just do the return i915_gem_open(dev, file) version like
you had originally.
Thanks,
Jani.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---
>
> drivers/gpu/drm/i915/i915_drv.c | 13 +------------
> 1 file changed, 1 insertion(+), 12 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
> index 7f4e8ad..d3a33c4 100644
> --- a/drivers/gpu/drm/i915/i915_drv.c
> +++ b/drivers/gpu/drm/i915/i915_drv.c
> @@ -1322,17 +1322,6 @@ void i915_driver_unload(struct drm_device *dev)
> i915_driver_cleanup_early(dev_priv);
> }
>
> -static int i915_driver_open(struct drm_device *dev, struct drm_file *file)
> -{
> - int ret;
> -
> - ret = i915_gem_open(dev, file);
> - if (ret)
> - return ret;
> -
> - return 0;
> -}
> -
> /**
> * i915_driver_lastclose - clean up after all DRM clients have exited
> * @dev: DRM device
> @@ -2569,7 +2558,7 @@ static int intel_runtime_resume(struct device *kdev)
> .driver_features =
> DRIVER_HAVE_IRQ | DRIVER_IRQ_SHARED | DRIVER_GEM | DRIVER_PRIME |
> DRIVER_RENDER | DRIVER_MODESET,
> - .open = i915_driver_open,
> + .open = i915_gem_open,
> .lastclose = i915_driver_lastclose,
> .preclose = i915_driver_preclose,
> .postclose = i915_driver_postclose,
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2016-09-15 9:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 14:39 [PATCH v2 0/5] drm: clean up several wrapper functions Masahiro Yamada
2016-09-14 14:39 ` [PATCH v2 1/5] drm/amdgpu: squash lines for simple " Masahiro Yamada
2016-09-15 14:45 ` Sean Paul
2016-09-14 14:39 ` [PATCH v2 2/5] drm/radeon: " Masahiro Yamada
2016-09-15 14:45 ` Sean Paul
2016-09-14 14:39 ` [PATCH v2 3/5] drm/bridge: " Masahiro Yamada
2016-09-15 13:51 ` Sean Paul
2016-09-15 14:46 ` Sean Paul
2016-09-16 1:41 ` Masahiro Yamada
2016-09-14 14:39 ` [PATCH v2 4/5] drm/qxl: " Masahiro Yamada
2016-09-15 12:30 ` Gustavo Padovan
2016-09-15 13:47 ` Gustavo Padovan
2016-09-15 14:45 ` Sean Paul
2016-09-14 14:39 ` [PATCH v2 5/5] drm/i915: use i915_gem_open() directly instead of i915_driver_open() Masahiro Yamada
2016-09-15 9:46 ` Jani Nikula [this message]
2016-09-15 9:48 ` Masahiro Yamada
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=87twdhpkba.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Alexander.Deucher@amd.com \
--cc=airlied@linux.ie \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yamada.masahiro@socionext.com \
/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
all inboxes | Powered by JetHome®