From: Ben Dooks <ben-linux@fluff.org>
To: David Brownell <david-b@pacbell.net>
Cc: Ben Dooks <ben-linux@fluff.org>,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: GPIO: Fix probe() error return in gpio driver probes
Date: Mon, 15 Dec 2008 10:15:25 +0000 [thread overview]
Message-ID: <20081215101524.GA12431@fluff.org.uk> (raw)
In-Reply-To: <200812141611.17555.david-b@pacbell.net>
On Sun, Dec 14, 2008 at 04:11:17PM -0800, David Brownell wrote:
> On Sunday 14 December 2008, Ben Dooks wrote:
> > Has anyone reveiwed this patch? Are there any comments, or can this
> > be commited at somepoint (even if it is during the next merge window)?
>
> I was thinking that -EINVAL is almost the least informative
> diagnostic code possible, since so many places return it
> that it's usually hard to find out *which* invalid parameter
> triggered ...
>
> Is there a less-overloaded code you could return?
The only other ones that I think would be close are:
ENOTSUP Operation not supported (POSIX.1)
EPROTO Protocol error (POSIX.1)
ENOENT No such file or directory
EFAULT Bad address
Feedback welcone.
> I have no issue with the patch other than that.
>
> - Dave
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Ben (ben@fluff.org, http://www.fluff.org/)
'a smiley only costs 4 bytes'
next prev parent reply other threads:[~2008-12-15 10:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 15:24 GPIO: Fix probe() error return in gpio driver probes Ben Dooks
2008-12-14 21:33 ` Ben Dooks
2008-12-15 0:11 ` David Brownell
2008-12-15 7:46 ` Jean Delvare
2008-12-15 10:16 ` Ben Dooks
2008-12-15 10:22 ` Jean Delvare
2008-12-18 18:16 ` David Brownell
2008-12-18 22:29 ` Ben Dooks
2008-12-15 10:15 ` Ben Dooks [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-07 12:56 ben
2009-01-08 12:20 ` Ben Dooks
2009-01-07 13:03 Ben Dooks
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=20081215101524.GA12431@fluff.org.uk \
--to=ben-linux@fluff.org \
--cc=david-b@pacbell.net \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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