From: Nikolas Nyby <nikolas@gnu.org>
To: gustavo@padovan.org, maarten.lankhorst@linux.intel.com,
trivial@kernel.org, dri-devel@lists.freedesktop.org
Cc: Nikolas Nyby <nikolas@gnu.org>
Subject: [PATCH] gpu/drm: Fix trivial typo
Date: Mon, 27 Aug 2018 09:53:14 -0400 [thread overview]
Message-ID: <20180827135314.21416-1-nikolas@gnu.org> (raw)
Fix a typo in the drm_dev init and alloc docs: advertice -> advertise
Signed-off-by: Nikolas Nyby <nikolas@gnu.org>
---
drivers/gpu/drm/drm_drv.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/drm_drv.c b/drivers/gpu/drm/drm_drv.c
index ea4941da9b27..282b43c44aab 100644
--- a/drivers/gpu/drm/drm_drv.c
+++ b/drivers/gpu/drm/drm_drv.c
@@ -468,7 +468,7 @@ static void drm_fs_inode_free(struct inode *inode)
* @parent: Parent device object
*
* Initialize a new DRM device. No device registration is done.
- * Call drm_dev_register() to advertice the device to user space and register it
+ * Call drm_dev_register() to advertise the device to user space and register it
* with other core subsystems. This should be done last in the device
* initialization sequence to make sure userspace can't access an inconsistent
* state.
@@ -622,7 +622,7 @@ EXPORT_SYMBOL(drm_dev_fini);
* @parent: Parent device object
*
* Allocate and initialize a new DRM device. No device registration is done.
- * Call drm_dev_register() to advertice the device to user space and register it
+ * Call drm_dev_register() to advertise the device to user space and register it
* with other core subsystems. This should be done last in the device
* initialization sequence to make sure userspace can't access an inconsistent
* state.
--
2.18.0
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
reply other threads:[~2018-08-27 13:56 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=20180827135314.21416-1-nikolas@gnu.org \
--to=nikolas@gnu.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@padovan.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=trivial@kernel.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