linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: wharms@bfs.de (walter harms)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] arch/arm/mach-at91/clock.c: Add missing IS_ERR test
Date: Tue, 25 Jan 2011 12:12:45 +0100	[thread overview]
Message-ID: <4D3EB02D.6090302@bfs.de> (raw)
In-Reply-To: <20110125104333.GE11507@n2100.arm.linux.org.uk>



Am 25.01.2011 11:43, schrieb Russell King - ARM Linux:
> On Tue, Jan 25, 2011 at 11:33:16AM +0100, walter harms wrote:
>> Would it be more easy to return NULL in the error case of clk_get() instead
>> of ERR_PTR(-ENOENT) ?
>>
>> So the default could be return NULL and an architecture depending solution
>> replacing that.
> 
> That's not how the API is defined.  The API defines error-pointers to be
> errors, everything should be considered valid.  Please don't go down the
> route of doing something architecturally different from that.
> 
> What if, say, you couldn't return the struct clk because maybe it could
> only be controlled by one user?  Returning an EBUSY error pointer would
> indicate this condition.  What if the module providing the struct clk
> hasn't finished initializing - that's another reason for EBUSY rather
> than ENOENT.
> 
> Error codes are useful to describe why something failed.  NULL pointers
> can't do that.
> 

On Mon, 24 Jan 2011, Vasiliy Kulikov wrote:
> 
...
> clk_get() is defined per-architecture, sometimes it is NULL only.
>

So these is a bug ? They should return -ENOENT ?

The interessting question is: what to do with an error ?

Obviously some architecture can live with NULL, so it is not an critical
error. An the patch shows a code that is simply a return, not even the
user is informed that something did not work as expected.

  reply	other threads:[~2011-01-25 11:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1295898922-18822-1-git-send-email-julia@diku.dk>
2011-01-24 19:55 ` [PATCH 2/4] arch/arm/mach-at91/clock.c: Add missing IS_ERR test Julia Lawall
2011-01-24 19:56   ` Ryan Mallon
2011-01-24 20:00     ` Julia Lawall
2011-01-24 20:05       ` Vasiliy Kulikov
2011-01-24 20:09         ` Julia Lawall
2011-01-24 20:14           ` Vasiliy Kulikov
2011-01-25 10:33           ` walter harms
2011-01-25 10:43             ` Russell King - ARM Linux
2011-01-25 11:12               ` walter harms [this message]
2011-01-25 11:17                 ` Russell King - ARM Linux
2011-01-25 11:18                 ` Julia Lawall
2011-01-25 11:26                   ` Russell King - ARM Linux
2011-01-25 11:31                     ` Julia Lawall
2011-01-24 20:11         ` Ryan Mallon
2011-01-24 20:28           ` Julia Lawall
2011-01-24 20:38             ` Ryan Mallon
2011-01-24 21:01               ` Julia Lawall
2011-01-24 21:06                 ` Ryan Mallon
2011-01-24 21:31                   ` Julia Lawall
2011-01-24 21:51                     ` Ryan Mallon
2011-01-24 23:23                       ` Russell King - ARM Linux
2011-01-25  1:44                         ` Jean-Christophe PLAGNIOL-VILLARD
2011-01-25  6:12                           ` Julia Lawall
2011-01-25 17:23                             ` Jean-Christophe PLAGNIOL-VILLARD
2011-01-24 19:55 ` [PATCH 4/4] arch/arm/mach-omap2/smartreflex.c: " Julia Lawall
2011-01-24 21:24   ` Kevin Hilman

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=4D3EB02D.6090302@bfs.de \
    --to=wharms@bfs.de \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).