From: Gwan-gyeong Mun <elongbug@gmail.com>
To: Daniel Vetter <daniel.vetter@intel.com>
Cc: Gustavo Padovan <gustavo@padovan.org>,
Sean Paul <seanpaul@chromium.org>,
David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Gwan-gyeong Mun <elongbug@gmail.com>
Subject: [PATCH] drm: Fix typo in lastclose description
Date: Sat, 3 Mar 2018 15:52:11 +0900 [thread overview]
Message-ID: <20180303065211.28513-1-elongbug@gmail.com> (raw)
ownershipe -> ownership
Signed-off-by: Mun Gwan-gyeong <elongbug@gmail.com>
---
include/drm/drm_drv.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/drm/drm_drv.h b/include/drm/drm_drv.h
index d23dcdd1bd95..64cb5975613c 100644
--- a/include/drm/drm_drv.h
+++ b/include/drm/drm_drv.h
@@ -140,7 +140,7 @@ struct drm_driver {
*
* All legacy drivers use this callback to de-initialize the hardware.
* This is purely because of the shadow-attach model, where the DRM
- * kernel driver does not really own the hardware. Instead ownershipe is
+ * kernel driver does not really own the hardware. Instead ownership is
* handled with the help of userspace through an inheritedly racy dance
* to set/unset the VT into raw mode.
*
--
2.16.2
reply other threads:[~2018-03-03 6:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180303065211.28513-1-elongbug@gmail.com \
--to=elongbug@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@padovan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanpaul@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox