mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kenneth Aafløy" <lists@kenneth.aafloy.net>
To: linux-kernel@vger.kernel.org
Subject: Coding style: mixed-case
Date: Wed, 6 Apr 2005 03:29:21 +0200	[thread overview]
Message-ID: <200504060329.21469.lists@kenneth.aafloy.net> (raw)

Hi,

while reading Documentation/CodingStyle for the nth time, I realized that I had
read some conflicting coding style in some patch posted to the linux-kernel
mailing-list; in include/linux/page-flags.h, there is a lot of defines that are
apparently frowned upon:

HOWEVER, while mixed-case names are frowned upon, descriptive names for
global variables are a must.  To call a global function "foo" is a
shooting offense.

Are those an exception to the rule or would for example PF_LOCKED/pf_locked be
a nice replacement for PageLocked?

Just wondering; with no intention to change code that I do not understand :)

Kenneth

             reply	other threads:[~2005-04-06  1:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-06  1:29 Kenneth Aafløy [this message]
2005-04-06  2:09 ` Matt Mackall
2005-04-06  2:37   ` Kenneth Aafløy
2005-04-06  9:01     ` Nick Piggin
2005-04-06 12:22       ` Hugh Dickins

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=200504060329.21469.lists@kenneth.aafloy.net \
    --to=lists@kenneth.aafloy.net \
    --cc=linux-kernel@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®