From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] [v2] tsec: fix the return value for tsec_eth_init() and tsec_standard_init()
Date: Mon, 07 Jun 2010 17:55:18 -0500 [thread overview]
Message-ID: <4C0D78D6.2010707@freescale.com> (raw)
In-Reply-To: <201006071849.29511.vapier@gentoo.org>
Mike Frysinger wrote:
> On Monday, June 07, 2010 14:31:27 Timur Tabi wrote:
>> In general, if an function initializes only one device, then it should
>> return a negative number if there's an error. If it initializes more than
>> one device, then it should never return a negative number. This is why
>> these functions now return an unsigned integer.
>
> i dont think this is a good idea. either the init funcs should all be
> converted to unsigned int, or they should stay int. doing it piecemeal leads
> to confusion with zero upside.
I don't want to change all of the functions. For most devices, there's no
way I can test them.
Just because pci_eth_int() is incorrect, that doesn't mean that I can't make
tsec_eth_init() correct.
> your fixes no way require these to be unsigned int funcs.
What's the point of making the return value a signed integer if it can never
be a negative number? The reason I changed the type to unsigned int is to
make it very clear that it will never return an error code.
next prev parent reply other threads:[~2010-06-07 22:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 18:31 [U-Boot] [PATCH] [v2] tsec: fix the return value for tsec_eth_init() and tsec_standard_init() Timur Tabi
2010-06-07 22:49 ` Mike Frysinger
2010-06-07 22:55 ` Timur Tabi [this message]
2010-06-08 4:04 ` Mike Frysinger
2010-06-08 14:34 ` Timur Tabi
2010-06-08 14:42 ` Reinhard Meyer
2010-06-08 14:55 ` Timur Tabi
2010-06-08 19:25 ` Mike Frysinger
2010-06-08 7:14 ` Wolfgang Denk
2010-06-08 13:01 ` Timur Tabi
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=4C0D78D6.2010707@freescale.com \
--to=timur@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.