LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Arnold <rsa@us.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Change H_StudlyCaps to H_SHOUTING_CAPS
Date: Thu, 30 Mar 2006 09:36:39 -0600	[thread overview]
Message-ID: <1143733000.14254.14.camel@localhost.localdomain> (raw)
In-Reply-To: <20060330115817.ADB99211AE9@Schermpje.local>

On Thu, 2006-03-30 at 13:58 +0200, Segher Boessenkool wrote:
> [I hope I got my mailer script to work okay, don't kill me please.]
> 
> Also cleans up some nearby whitespace problems.
> 
> Signed-of-by: Segher Boessenkool <segher@kernel.crashing.org>

> -	else if (rc == H_Parameter)
> +		       "plpar-hcall (%s) failed; not authorized to this"
> +		       " function\n", tag);
> +	else if (rc == H_PARAMETER)
>  		printk(KERN_INFO "plpar-hcall (%s) failed; Bad parameter(s)\n",
>  		       tag);

I believe the studly caps were used over shouting caps because the RPA
specification, from which these ret codes were taken, uses Studly Caps.
That probably isn't sufficient justification, just an historical
perspective.

-- 
Ryan S. Arnold <rsa@us.ibm.com>
IBM Linux Technology Center
Linux on Power Toolchain

  reply	other threads:[~2006-03-30 20:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-30 11:58 [PATCH] Change H_StudlyCaps to H_SHOUTING_CAPS Segher Boessenkool
2006-03-30 15:36 ` Ryan Arnold [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-30 12:49 Segher Boessenkool

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=1143733000.14254.14.camel@localhost.localdomain \
    --to=rsa@us.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=segher@kernel.crashing.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