public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fs/fat: add a parameter: allow_whole_dev to fat_register_device()
Date: Fri, 13 Jun 2014 09:40:33 -0400	[thread overview]
Message-ID: <20140613134033.GD5752@bill-the-cat> (raw)
In-Reply-To: <539A70FF.4080003@atmel.com>

On Fri, Jun 13, 2014 at 11:33:19AM +0800, Josh Wu wrote:

> Dear Wolfgang
> 
> On 6/12/2014 4:52 PM, Wolfgang Denk wrote:
> >Dear Josh Wu,
> >
> >In message <53995100.9080307@atmel.com> you wrote:

I will read and think about the rest of this, but:

[snip]
> >>>>+int fat_register_device(block_dev_desc_t *dev_desc, int part_no,
> >>>>+			bool allow_whole_dev);
> >>>Please make this an "int" type, and use 0 and 1.
> >>Is there any special concern for that? like cause machine compatiable issue?
> >Boolean values in C are 1 and 0.  Hiding these under other names (like
> >"true" and "false") doesn't buy anything.
> 
> Okay. I just think use bool will be more readable. That also can
> make people less use an integer number, which in some case it's hard
> to understand it.

We have bool and make use of bool when things are a boolean, your way
here is fine.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140613/601926a4/attachment.pgp>

      parent reply	other threads:[~2014-06-13 13:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-12  5:57 [U-Boot] [PATCH] fs/fat: add a parameter: allow_whole_dev to fat_register_device() Josh Wu
2014-06-12  6:26 ` Wolfgang Denk
2014-06-12  7:04   ` Josh Wu
2014-06-12  8:52     ` Wolfgang Denk
2014-06-13  3:33       ` Josh Wu
2014-06-13  4:07         ` Stephen Warren
2014-06-13  4:54           ` Josh Wu
2014-06-14 20:07             ` Tom Rini
2014-06-13  4:38         ` Wolfgang Denk
2014-06-13 13:40         ` Tom Rini [this message]

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=20140613134033.GD5752@bill-the-cat \
    --to=trini@ti.com \
    --cc=u-boot@lists.denx.de \
    /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