From: Daniel Vetter <daniel@ffwll.ch>
To: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
Cc: Alan <gnomes@lxorguk.ukuu.org.uk>,
wuninsu@gmail.com, linux-kernel <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] gma500: clean up an excessive and confusing helper
Date: Mon, 8 Feb 2016 10:07:36 +0100 [thread overview]
Message-ID: <20160208090736.GW11240@phenom.ffwll.local> (raw)
In-Reply-To: <CAMeQTsakXL5DgdnozTzTXeu0W8yFa4EY4q-Q57Q20wHiVUMjoA@mail.gmail.com>
On Mon, Feb 01, 2016 at 09:11:51AM +0100, Patrik Jakobsson wrote:
> On Fri, Jan 29, 2016 at 8:37 PM, Alan <gnomes@lxorguk.ukuu.org.uk> wrote:
> > From: Alan Cox <alan@linux.intel.com>
> >
> > This is a left over from the great clean ups in the past. It's confusing as
> > it returns an int, yet has one caller that never uses it. The caller already
> > has all the right private variables local so the entire function can be
> > replaced by a simple if call.
> >
> > Signed-off-by: Alan Cox <alan@linux.intel.com>
>
> Signed-off-by: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
Applied to drm-misc, thanks.
-Daniel
>
> > ---
> > drivers/gpu/drm/gma500/framebuffer.c | 20 ++++----------------
> > 1 file changed, 4 insertions(+), 16 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/gma500/framebuffer.c b/drivers/gpu/drm/gma500/framebuffer.c
> > index cb95765..033d894 100644
> > --- a/drivers/gpu/drm/gma500/framebuffer.c
> > +++ b/drivers/gpu/drm/gma500/framebuffer.c
> > @@ -674,29 +674,17 @@ static const struct drm_mode_config_funcs psb_mode_funcs = {
> > .output_poll_changed = psbfb_output_poll_changed,
> > };
> >
> > -static int psb_create_backlight_property(struct drm_device *dev)
> > -{
> > - struct drm_psb_private *dev_priv = dev->dev_private;
> > - struct drm_property *backlight;
> > -
> > - if (dev_priv->backlight_property)
> > - return 0;
> > -
> > - backlight = drm_property_create_range(dev, 0, "backlight", 0, 100);
> > -
> > - dev_priv->backlight_property = backlight;
> > -
> > - return 0;
> > -}
> > -
> > static void psb_setup_outputs(struct drm_device *dev)
> > {
> > struct drm_psb_private *dev_priv = dev->dev_private;
> > struct drm_connector *connector;
> >
> > drm_mode_create_scaling_mode_property(dev);
> > - psb_create_backlight_property(dev);
> >
> > + /* It is ok for this to fail - we just don't get backlight control */
> > + if (!dev_priv->backlight_property)
> > + dev_priv->backlight_property = drm_property_create_range(dev, 0,
> > + "backlight", 0, 100);
> > dev_priv->ops->output_init(dev);
> >
> > list_for_each_entry(connector, &dev->mode_config.connector_list,
> >
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2016-02-08 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 19:37 Alan
2016-02-01 8:11 ` Patrik Jakobsson
2016-02-08 9:07 ` Daniel Vetter [this message]
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=20160208090736.GW11240@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=patrik.r.jakobsson@gmail.com \
--cc=wuninsu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®