From: David Miller <davem@davemloft.net>
To: jj@chaosbits.net
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] Sparc: Remove trigraph in die_if_kernel() message.
Date: Thu, 09 Jun 2011 15:59:43 -0700 (PDT) [thread overview]
Message-ID: <20110609.155943.162785602513776337.davem@davemloft.net> (raw)
In-Reply-To: <alpine.LNX.2.00.1106071627260.8844@swampdragon.chaosbits.net>
From: Jesper Juhl <jj@chaosbits.net>
Date: Tue, 7 Jun 2011 16:38:19 +0200 (CEST)
> In arch/sparc/kernel/traps_32.c::do_priv_instruction() we have this:
>
> die_if_kernel("Penguin instruction from Penguin mode??!?!", regs);
>
> If I'm not mistaken, that "??!" will be taken as a trigraph for "|" by the
> preprocessor, so the final string will end up either as
> "Penguin instruction from Penguin mode|?!"
> which I assume is not what we want, or as the correct string but with a
> warning about an ignored trigraph which I assume we don't want either. So,
> in order to elliminate the trigraph but keep the original string intact I
> changed it to
>
> die_if_kernel("Penguin instruction from Penguin mode?""?!?!", regs);
>
> I've tested with a small test program on my x86-64 host and it behaves as
> I would expect, but I've not tested the actual code in
> arch/sparc/kernel/traps_32.c since I have no way to compile for sparc
> (which is why I submit this as a [RFC] patch).
>
> Please take a look and apply if you agree :-)
>
> Signed-off-by: Jesper Juhl <jj@chaosbits.net>
Applied, thanks Jesper :-)
next prev parent reply other threads:[~2011-06-09 22:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 14:38 Jesper Juhl
2011-06-09 22:59 ` David Miller [this message]
2011-06-09 23:03 ` Al Viro
2011-06-09 23:06 ` David Miller
2011-06-10 7:51 ` Jesper Juhl
2011-06-12 7:23 ` Daniel K.
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=20110609.155943.162785602513776337.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jj@chaosbits.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@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
all inboxes | Powered by JetHome®