From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Cc: DRI Development <dri-devel@lists.freedesktop.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
Cao Minh Hiep <cm-hiep@jinso.co.jp>
Subject: Re: [PATCH 3/3] drm: rcar-du: Convert rcar_du_encoders_init_one() return value to 0/<0
Date: Tue, 26 May 2015 21:24:03 +0200 [thread overview]
Message-ID: <CAMuHMdWYUnY82cFeeZePOqu3VwLP_gq95a0K4qDJLGx+utLWJQ@mail.gmail.com> (raw)
In-Reply-To: <1432652516-15085-4-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
On Tue, May 26, 2015 at 5:01 PM, Laurent Pinchart
<laurent.pinchart+renesas@ideasonboard.com> wrote:
> --- a/drivers/gpu/drm/rcar-du/rcar_du_kms.c
> +++ b/drivers/gpu/drm/rcar-du/rcar_du_kms.c
> @@ -640,14 +640,14 @@ static int rcar_du_encoders_init_one(struct rcar_du_device *rcdu,
> of_node_put(connector);
>
> if (!ret)
> - return 1;
> + return 0;
>
> if (ret != -EPROBE_DEFER)
> dev_warn(rcdu->dev,
> "failed to initialize encoder %s (%d), skipping\n",
> encoder->full_name, ret);
>
> - return 0;
> + return ret;
> }
Perhaps just
if (ret && ret != -EPROBE_DEFER)
dev_warn(...);
return ret;
?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2015-05-26 19:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 15:01 [PATCH 0/3] R-Car DU fixes Laurent Pinchart
2015-05-26 15:01 ` [PATCH 1/3] drm: rcar-du: Fix crash with groups that have less than 9 planes Laurent Pinchart
2015-05-26 15:01 ` [PATCH 2/3] drm: rcar-du: Clarify error message when encoder initialization fails Laurent Pinchart
2015-05-26 15:01 ` [PATCH 3/3] drm: rcar-du: Convert rcar_du_encoders_init_one() return value to 0/<0 Laurent Pinchart
2015-05-26 19:24 ` Geert Uytterhoeven [this message]
2015-06-16 10:57 ` Laurent Pinchart
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=CAMuHMdWYUnY82cFeeZePOqu3VwLP_gq95a0K4qDJLGx+utLWJQ@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=cm-hiep@jinso.co.jp \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-sh@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;
as well as URLs for NNTP newsgroup(s).