mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Kleikamp <shaggy@austin.ibm.com>
To: Richard Knutsson <ricknu-0@student.ltu.se>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, hch@infradead.org
Subject: Re: [PATCH 2.6.18-rc4-mm2] fs/jfs: Conversion to generic boolean
Date: Mon, 28 Aug 2006 16:11:32 -0500	[thread overview]
Message-ID: <1156799492.8732.19.camel@kleikamp.austin.ibm.com> (raw)
In-Reply-To: <44F35537.6000308@student.ltu.se>

On Mon, 2006-08-28 at 22:42 +0200, Richard Knutsson wrote:

> Just why is it, that when there is a change to make locally defined 
> booleans into a more generic one, it is converted into integers? ;)

I just see this as an opportunity to make jfs more closely fit the
coding style of the mainline kernel.

> But seriously, what is gained by removing them, other then less 
> understandable code? (Not talking about FALSE -> 0, but boolean_t -> int)

I don't feel strongly one way or another about the use of boolean_t, but
under fs/, the only code that uses that type is in fs/jfs and fs/xfs,
which are both ported from other operating systems.  Using ints for
boolean values does seem to be the accepted practice in the kernel.

> I can understand if authors disprove making an integer into a boolean, 
> but here it already were booleans.
> But hey, you are the maintainer ;)

I could be persuaded to leave the declarations as boolean_t or even
making them bool, but right now I'm leaning toward making them int for
consistency.

Shaggy
-- 
David Kleikamp
IBM Linux Technology Center


  reply	other threads:[~2006-08-28 21:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-26 17:37 Richard Knutsson
2006-08-28 14:22 ` Dave Kleikamp
2006-08-28 20:42   ` Richard Knutsson
2006-08-28 21:11     ` Dave Kleikamp [this message]
2006-08-28 23:33       ` Richard Knutsson
2006-08-29 12:37         ` Dave Kleikamp
2006-08-29 13:48           ` Richard Knutsson
2006-08-29 13:53             ` Dave Kleikamp

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=1156799492.8732.19.camel@kleikamp.austin.ibm.com \
    --to=shaggy@austin.ibm.com \
    --cc=akpm@osdl.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ricknu-0@student.ltu.se \
    /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®