public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: alext@fc.hp.com (Alex Tsariounov)
To: linux-ia64@vger.kernel.org
Subject: small syntax patch to entry.S
Date: Fri, 04 Jun 2004 18:49:10 +0000	[thread overview]
Message-ID: <20040604184909.GB2294@fc.hp.com> (raw)

Hello, David,

I looked on the latest bitkeeper ia64 tree (well, at least what I
thought was the latest...) and this one still seems to be there.
It doesn't seem to bother the assembler, but it gives my syntax
colorizer the chills.

Thanks,
Alex


diff -Nru -X dontdiff linux-2.6.6/arch/ia64/kernel/entry.S linux-2.6.6.fix/arch/ia64/kernel/entry.S
--- linux-2.6.6/arch/ia64/kernel/entry.S	2004-06-04 12:32:57.000000000 -0600
+++ linux-2.6.6.fix/arch/ia64/kernel/entry.S	2004-06-04 12:34:09.000000000 -0600
@@ -21,7 +21,7 @@
  * Jonathan Nicklin	<nicklin@missioncriticallinux.com>
  * Patrick O'Rourke	<orourke@missioncriticallinux.com>
  * 11/07/2000
- /
+ */
 /*
  * Global (preserved) predicate usage on syscall entry/exit path:
  *

                 reply	other threads:[~2004-06-04 18:49 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=20040604184909.GB2294@fc.hp.com \
    --to=alext@fc.hp.com \
    --cc=linux-ia64@vger.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