public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: trivial@kernel.org, lkml <linux-kernel@vger.kernel.org>
Cc: Paul Mackerras <paulus@au1.ibm.com>
Subject: [PATCH] trivial: use (C) instead of \251
Date: Wed, 28 Apr 2010 11:30:31 +0200	[thread overview]
Message-ID: <4BD80037.9060704@kernel.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 976 bytes --]

The latin-1 copyright character \251 is invalid in ASCII or UTF-8 and
causes annoying problems with some editors and tools.  Use (C)
instead.

Signed-off-by: Tejun Heo <tj@kernel.org>
Cc: Paul Mackerras <paulus@au1.ibm.com>
---
I'm not really sure this would survive transport over mail in
appliable form, attaching the patch too just in case.

 kernel/perf_event.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/perf_event.c b/kernel/perf_event.c
index 2f3fbf8..827ec53 100644
--- a/kernel/perf_event.c
+++ b/kernel/perf_event.c
@@ -4,7 +4,7 @@
  *  Copyright (C) 2008 Thomas Gleixner <tglx@linutronix.de>
  *  Copyright (C) 2008-2009 Red Hat, Inc., Ingo Molnar
  *  Copyright (C) 2008-2009 Red Hat, Inc., Peter Zijlstra <pzijlstr@redhat.com>
- *  Copyright  ©  2009 Paul Mackerras, IBM Corp. <paulus@au1.ibm.com>
+ *  Copyright (C) 2009 Paul Mackerras, IBM Corp. <paulus@au1.ibm.com>
  *
  * For licensing details see kernel-base/COPYING
  */

[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 910 bytes --]

Subject: [PATCH] trivial: use (C) instead of \251

The latin-1 copyright character \251 is invalid in ASCII or UTF-8 and
causes annoying problems with some editors and tools.  Use (C)
instead.

Signed-off-by: Tejun Heo <tj@kernel.org>
Cc: Paul Mackerras <paulus@au1.ibm.com>
---
 kernel/perf_event.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/perf_event.c b/kernel/perf_event.c
index 2f3fbf8..827ec53 100644
--- a/kernel/perf_event.c
+++ b/kernel/perf_event.c
@@ -4,7 +4,7 @@
  *  Copyright (C) 2008 Thomas Gleixner <tglx@linutronix.de>
  *  Copyright (C) 2008-2009 Red Hat, Inc., Ingo Molnar
  *  Copyright (C) 2008-2009 Red Hat, Inc., Peter Zijlstra <pzijlstr@redhat.com>
- *  Copyright  ©  2009 Paul Mackerras, IBM Corp. <paulus@au1.ibm.com>
+ *  Copyright (C) 2009 Paul Mackerras, IBM Corp. <paulus@au1.ibm.com>
  *
  * For licensing details see kernel-base/COPYING
  */

             reply	other threads:[~2010-04-28  9:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-28  9:30 Tejun Heo [this message]
2010-04-28 18:42 ` [PATCH] trivial: use (C) instead of \251 Harald Arnesen
2010-04-28 20:20   ` Tejun Heo
2010-04-29 10:34     ` Harald Arnesen
2010-04-28 21:55 ` Paul Mackerras
2010-04-29  5:32   ` Tejun Heo
2010-04-28 22:41 ` Jiri Kosina
2010-04-29  4:57   ` Paul Mackerras
2010-04-29  5:35     ` Tejun Heo
2010-04-30  7:55   ` Ingo Molnar
2010-04-30  7:59     ` Tejun Heo
2010-04-30 22:18       ` H. Peter Anvin
2010-04-30  8:01     ` Jiri Kosina
2010-04-30  8:37       ` Ingo Molnar
2010-04-30  9:04         ` Jiri Kosina
2010-04-30  9:28           ` Ingo Molnar
2010-05-01  0:34           ` Paul Mackerras

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=4BD80037.9060704@kernel.org \
    --to=tj@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@au1.ibm.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