From mboxrd@z Thu Jan  1 00:00:00 1970
From: Timur Tabi <timur@freescale.com>
Date: Fri, 04 Jun 2010 16:42:05 -0500
Subject: [U-Boot] [PATCH] tsec: fix the return value for tsec_eth_init()
In-Reply-To: <FBFF9378-18C0-425D-896D-477E8673372B@freescale.com>
References: <1275684642-17608-1-git-send-email-timur@freescale.com>
	<254C866E-B460-47D7-8CCC-9C8F200189C1@freescale.com>
	<4C096995.4090101@freescale.com>
	<FBFF9378-18C0-425D-896D-477E8673372B@freescale.com>
Message-ID: <4C09732D.1050608@freescale.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Andy Fleming wrote:
> You just noted that tsec_eth_init should return the number of tsecs
> initialized successfully.  Therefore, the callers can check that number,
> and respond accordingly.  tsec_initialize() can report the error.  If we
> want more elaborate error handling, we can devise something.  But with
> the new scheme, an error in one tsec (like a riser card not being plugged
> in) will cause all of the tsecs to not be initialized, which seems
> silly.

Ok, so the rule is: a function which initializes one interface can return an
error <0, but a function which initializes multiple interfaces should not.
V2 coming right up.