From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] hvc_dcc: don't ignore errors during initialization
Date: Wed, 01 Jul 2015 16:54:53 -0700 [thread overview]
Message-ID: <55947DCD.1020605@codeaurora.org> (raw)
In-Reply-To: <1435699387-32591-2-git-send-email-timur@codeaurora.org>
On 06/30/2015 02:23 PM, Timur Tabi wrote:
> hvc_instantiate() and hvc_alloc() return errors if they fail, so don't
> ignore them.
>
> Signed-off-by: Timur Tabi <timur@codeaurora.org>
> ---
> drivers/tty/hvc/hvc_dcc.c | 17 +++++++++++++----
> 1 file changed, 13 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/tty/hvc/hvc_dcc.c b/drivers/tty/hvc/hvc_dcc.c
> index 33657dc..f8b8cf2 100644
> --- a/drivers/tty/hvc/hvc_dcc.c
> +++ b/drivers/tty/hvc/hvc_dcc.c
> @@ -225,20 +225,29 @@ static const struct hv_ops hvc_dcc_get_put_ops = {
>
> static int __init hvc_dcc_console_init(void)
> {
> + int ret;
> +
> + /* This always runs on boot core */
> if (!hvc_dcc_check())
> return -ENODEV;
>
> - hvc_instantiate(0, 0, &hvc_dcc_get_put_ops);
> - return 0;
> + /* Returns -1 if error */
> + ret = hvc_instantiate(0, 0, &hvc_dcc_get_put_ops);
> +
> + return ret < 0 ? -ENODEV : 0;
Why not just return the value that hvc_instantiate returns? And maybe we
should change those -1 in hvc_instantiate into -EPERM?
> }
> console_initcall(hvc_dcc_console_init);
>
> static int __init hvc_dcc_init(void)
> {
> + struct hvc_struct *p;
> +
> + /* This can run on any core */
> if (!hvc_dcc_check())
> return -ENODEV;
>
> - hvc_alloc(0, 0, &hvc_dcc_get_put_ops, 128);
> - return 0;
> + p = hvc_alloc(0, 0, &hvc_dcc_get_put_ops, 128);
> +
> + return IS_ERR(p) ? PTR_ERR(p) : 0;
return PTR_ERR_OR_ZERO()?
> }
> device_initcall(hvc_dcc_init);
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-07-01 23:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 21:23 [PATCH 1/4] hvc_dcc: bind driver to core0 for reads and writes Timur Tabi
2015-06-30 21:23 ` [PATCH 2/4] hvc_dcc: don't ignore errors during initialization Timur Tabi
2015-07-01 23:54 ` Stephen Boyd [this message]
2015-07-03 14:46 ` Timur Tabi
2015-06-30 21:23 ` [PATCH 3/4] [v3] ARM64: TTY: hvc_dcc: Add support for ARM64 dcc Timur Tabi
2015-06-30 21:23 ` [PATCH 4/4] hvc_dcc: disable user-space access to DCC Timur Tabi
2015-07-02 0:00 ` Stephen Boyd
2015-07-03 14:53 ` Timur Tabi
2015-07-01 1:37 ` [PATCH 1/4] hvc_dcc: bind driver to core0 for reads and writes Stephen Boyd
2015-07-01 1:57 ` Timur Tabi
2015-07-01 23:38 ` Stephen Boyd
2015-07-03 14:42 ` Timur Tabi
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=55947DCD.1020605@codeaurora.org \
--to=sboyd@codeaurora.org \
--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).