From: Kevin Hilman <khilman@deeprootsystems.com>
To: romit@ti.com
Cc: nm@ti.com, linux-omap@vger.kernel.org
Subject: Re: [PM-WIP-OPP] [PATCH 2/2]: Change return value from ERR_PTR(..) to NULL in opp layer
Date: Fri, 15 Jan 2010 10:12:17 -0800 [thread overview]
Message-ID: <878wbz44qm.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1263553383.3490.44.camel@boson> (Romit Dasgupta's message of "Fri\, 15 Jan 2010 16\:33\:03 +0530")
Romit Dasgupta <romit@ti.com> writes:
> Returning NULL pointer from the OPP APIs instead of ERR_PTR where
> return struct omap_opp *. This is because there is no inherent value in
> returning ERR_PTR from the opp layer. Returning NULL serves the purpose.
NAK.
Using ERR_PTR allows returning different types of error conditions,
and is common practice across the kernel.
Kevin
> Signed-off-by: Romit Dasgupta <romit@ti.com>
> ---
>
> diff --git a/arch/arm/mach-omap2/resource34xx.c b/arch/arm/mach-omap2/resource34xx.c
> index 5ec072e..9572062 100644
> --- a/arch/arm/mach-omap2/resource34xx.c
> +++ b/arch/arm/mach-omap2/resource34xx.c
> @@ -202,7 +202,7 @@ static int __deprecated freq_to_opp(u8 *opp_id, enum opp_t opp_t,
>
> BUG_ON(opp_t >= OPP_TYPES_MAX);
> opp = opp_find_freq_ceil(opp_t, &freq);
> - if (IS_ERR(opp))
> + if (!opp)
> return -EINVAL;
> *opp_id = opp_get_opp_id(opp);
> return 0;
> diff --git a/arch/arm/plat-omap/opp.c b/arch/arm/plat-omap/opp.c
> index 8fd9366..7835b5d 100644
> --- a/arch/arm/plat-omap/opp.c
> +++ b/arch/arm/plat-omap/opp.c
> @@ -129,7 +129,7 @@ struct omap_opp *opp_find_freq_exact(enum opp_t opp_t,
>
> if (unlikely(opp_t >= OPP_TYPES_MAX)) {
> pr_err("%s: Invalid parameters being passed\n", __func__);
> - return ERR_PTR(-EINVAL);
> + return NULL;
> }
>
> oppl = _opp_list[opp_t];
> @@ -143,7 +143,7 @@ struct omap_opp *opp_find_freq_exact(enum opp_t opp_t,
> oppl++;
> }
>
> - return OPP_TERM(oppl) ? ERR_PTR(-ENOENT) : oppl;
> + return OPP_TERM(oppl) ? NULL : oppl;
> }
>
> struct omap_opp *opp_find_freq_ceil(enum opp_t opp_t, unsigned long *freq)
> @@ -153,7 +153,7 @@ struct omap_opp *opp_find_freq_ceil(enum opp_t opp_t, unsigned long *freq)
> if (unlikely(opp_t >= OPP_TYPES_MAX || !freq ||
> IS_ERR(freq))) {
> pr_err("%s: Invalid parameters being passed\n", __func__);
> - return ERR_PTR(-EINVAL);
> + return NULL;
> }
>
> oppl = _opp_list[opp_t];
> @@ -169,7 +169,7 @@ struct omap_opp *opp_find_freq_ceil(enum opp_t opp_t, unsigned long *freq)
> }
>
> if (OPP_TERM(oppl))
> - return ERR_PTR(-ENOENT);
> + return NULL;
>
> *freq = oppl->rate;
>
> @@ -183,7 +183,7 @@ struct omap_opp *opp_find_freq_floor(enum opp_t opp_t, unsigned long *freq)
> if (unlikely(opp_t >= OPP_TYPES_MAX || !freq ||
> IS_ERR(freq))) {
> pr_err("%s: Invalid parameters being passed\n", __func__);
> - return ERR_PTR(-EINVAL);
> + return NULL;
> }
> oppl = prev_opp = _opp_list[opp_t];
>
> @@ -202,7 +202,7 @@ struct omap_opp *opp_find_freq_floor(enum opp_t opp_t, unsigned long *freq)
> }
>
> if (prev_opp->rate > *freq)
> - return ERR_PTR(-ENOENT);
> + return NULL;
>
> *freq = prev_opp->rate;
>
next prev parent reply other threads:[~2010-01-15 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 11:03 [PM-WIP-OPP] [PATCH 2/2]: Change return value from ERR_PTR(..) to NULL in opp layer Romit Dasgupta
2010-01-15 18:12 ` Kevin Hilman [this message]
2010-01-16 2:36 ` Dasgupta, Romit
2010-01-16 2:54 ` Nishanth Menon
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=878wbz44qm.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=romit@ti.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.