From: Jiri Slaby <jirislaby@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linville@tuxdriver.com, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, ath5k-devel@lists.ath5k.org,
Nick Kossifidis <mickflemm@gmail.com>
Subject: Re: [PATCH 2/3] WDEV, ath5k, don't return int from bool function
Date: Fri, 15 Feb 2008 23:38:43 +0100 [thread overview]
Message-ID: <47B61473.7060206@gmail.com> (raw)
In-Reply-To: <43e72e890802151408g35fa2e49r5eb8557e4a5bbce4@mail.gmail.com>
On 02/15/2008 11:08 PM, Luis R. Rodriguez wrote:
> On Fri, Feb 15, 2008 at 3:58 PM, Jiri Slaby <jirislaby@gmail.com> wrote:
>
>> -static bool
>> +static int
>> ath5k_hw_setup_xr_tx_desc(struct ath5k_hw *ah, struct ath5k_desc *desc,
>> unsigned int tx_rate1, u_int tx_tries1, u_int tx_rate2, u_int tx_tries2,
>> unsigned int tx_rate3, u_int tx_tries3)
>> @@ -3773,10 +3773,10 @@ ath5k_hw_setup_xr_tx_desc(struct ath5k_hw *ah, struct ath5k_desc *desc,
>>
>> #undef _XTX_TRIES
>>
>> - return true;
>> + return 1;
>> }
>>
>> - return false;
>> + return 0;
>> }
>
> Shouldn't we then treat 0 as OK?
Sorry, I don't understand you. There is return -EINVAL in the function above
this too and we need to cope with another two states but the error: it is
supported/it isn't. You mean to consider 0 as supported, -ENODEV/-EOPNOTSUPP as
unsupported and the rest as error?
next prev parent reply other threads:[~2008-02-15 22:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 20:58 [PATCH 1/3] WDEV: ath5k, fix lock imbalance Jiri Slaby
2008-02-15 20:58 ` [PATCH 2/3] WDEV, ath5k, don't return int from bool function Jiri Slaby
2008-02-15 22:03 ` Nick Kossifidis
2008-02-15 22:08 ` Luis R. Rodriguez
2008-02-15 22:38 ` Jiri Slaby [this message]
2008-02-15 23:24 ` Luis R. Rodriguez
2008-02-15 23:29 ` Jiri Slaby
2008-02-15 20:58 ` [PATCH 3/3] WDEV: ath5k, typecheck on nonDEBUG Jiri Slaby
2008-02-15 22:32 ` Luis R. Rodriguez
2008-02-15 22:00 ` [PATCH 1/3] WDEV: ath5k, fix lock imbalance Nick Kossifidis
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=47B61473.7060206@gmail.com \
--to=jirislaby@gmail.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=mickflemm@gmail.com \
/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.