From: Joe Perches <joe@perches.com>
To: Jiri Kosina <trivial@kernel.org>
Cc: David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/9] drivers/gpu: typo fix of faild to failed
Date: Thu, 21 Oct 2010 22:17:13 -0700 [thread overview]
Message-ID: <9109bfa77cbbc07631bd3dbef70ba219d4054682.1287724261.git.joe@perches.com> (raw)
In-Reply-To: <cover.1287724261.git.joe@perches.com>
Signed-off-by: Joe Perches <joe@perches.com>
---
drivers/gpu/drm/radeon/radeon_cs.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/gpu/drm/radeon/radeon_cs.c b/drivers/gpu/drm/radeon/radeon_cs.c
index fcc79b5..6d64a27 100644
--- a/drivers/gpu/drm/radeon/radeon_cs.c
+++ b/drivers/gpu/drm/radeon/radeon_cs.c
@@ -268,7 +268,7 @@ int radeon_cs_ioctl(struct drm_device *dev, void *data, struct drm_file *filp)
}
r = radeon_ib_schedule(rdev, parser.ib);
if (r) {
- DRM_ERROR("Faild to schedule IB !\n");
+ DRM_ERROR("Failed to schedule IB !\n");
}
radeon_cs_parser_fini(&parser, r);
mutex_unlock(&rdev->cs_mutex);
--
1.7.3.1.g432b3.dirty
next prev parent reply other threads:[~2010-10-22 5:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 5:17 [PATCH 0/9] Typo fixes " Joe Perches
2010-10-22 5:17 ` [PATCH 1/9] drivers/ata: typo fix " Joe Perches
2010-10-22 5:17 ` Joe Perches [this message]
2010-10-22 5:17 ` [PATCH 3/9] drivers/net: " Joe Perches
2010-10-22 5:17 ` [PATCH 4/9] drivers/rtc: " Joe Perches
2010-10-22 5:21 ` Wan ZongShun
2010-10-22 5:17 ` [PATCH 5/9] drivers/video: " Joe Perches
2010-10-22 5:17 ` [PATCH 6/9] fs/exofs: " Joe Perches
2010-10-24 10:09 ` Boaz Harrosh
2010-10-22 5:17 ` [PATCH 7/9] fs/jfs: " Joe Perches
2010-10-22 5:17 ` [PATCH 8/9] kernel/trace: " Joe Perches
2010-10-23 19:43 ` [tip:perf/urgent] tracing: Fix 'faild' -> 'failed' typo tip-bot for Joe Perches
2010-10-22 5:17 ` [PATCH 9/9] net/wanrouter: typo fix of faild to failed Joe Perches
2010-10-22 20:15 ` [PATCH 0/9] Typo fixes " Mike Frysinger
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=9109bfa77cbbc07631bd3dbef70ba219d4054682.1287724261.git.joe@perches.com \
--to=joe@perches.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®