From: Jani Nikula <jani.nikula@linux.intel.com>
To: Julia Lawall <Julia.Lawall@lip6.fr>,
Daniel Vetter <daniel.vetter@intel.com>
Cc: kernel-janitors@vger.kernel.org, linux@rasmusvillemoes.dk,
joe@perches.com, David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 7/20] drm/i915: fix misspelling of current function in string
Date: Mon, 08 Dec 2014 12:24:27 +0200 [thread overview]
Message-ID: <87fvcqo2w4.fsf@intel.com> (raw)
In-Reply-To: <1417980062-25151-8-git-send-email-Julia.Lawall@lip6.fr>
On Sun, 07 Dec 2014, Julia Lawall <Julia.Lawall@lip6.fr> wrote:
> Replace a misspelled function name by %s and then __func__.
>
> This was done using Coccinelle, including the use of Levenshtein distance,
> as proposed by Rasmus Villemoes.
>
> Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>
>
> ---
> The semantic patch is difficult to summarize, but is available in the cover
> letter of this patch series.
>
> The message is sort of ambiguous, but I assume that it is intended to refer
> to the function in which the problem is detected.
Hmm, DRM_DEBUG prints __func__ too.
Jani.
>
> drivers/gpu/drm/i915/i915_gem.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> index d2ba315..fa21d1c 100644
> --- a/drivers/gpu/drm/i915/i915_gem.c
> +++ b/drivers/gpu/drm/i915/i915_gem.c
> @@ -4335,7 +4335,7 @@ i915_gem_unpin_ioctl(struct drm_device *dev, void *data,
> }
>
> if (obj->pin_filp != file) {
> - DRM_DEBUG("Not pinned by caller in i915_gem_pin_ioctl(): %d\n",
> + DRM_DEBUG("Not pinned by caller in %s(): %d\n", __func__,
> args->handle);
> ret = -EINVAL;
> goto out;
>
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-12-08 10:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-07 19:20 [PATCH 0/20] fix misspelling of current function in string Julia Lawall
2014-12-07 19:20 ` [PATCH 7/20] drm/i915: " Julia Lawall
2014-12-08 10:24 ` Jani Nikula [this message]
2014-12-08 14:15 ` Daniel Vetter
2014-12-07 23:44 ` [PATCH 0/20] " Julian Calaby
2014-12-08 6:43 ` Julia Lawall
2014-12-10 2:56 ` Julian Calaby
2014-12-08 3:55 ` Joe Perches
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=87fvcqo2w4.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Julia.Lawall@lip6.fr \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
/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