From: Dan Carpenter <dan.carpenter@oracle.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [patch 1/2] backlight: lm3630: signedness bug in lm3630a_chip_init()
Date: Thu, 26 Sep 2013 09:53:44 +0000 [thread overview]
Message-ID: <20130926095344.GA6247@mwanda> (raw)
In-Reply-To: <20130925085451.GA6661@elgon.mountain>
On Thu, Sep 26, 2013 at 12:43:43PM +0300, Tomi Valkeinen wrote:
> On 25/09/13 11:54, Dan Carpenter wrote:
> > "rval" needs to be signed for the error handling to work.
> >
> > Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> >
> > diff --git a/drivers/video/backlight/lm3630a_bl.c b/drivers/video/backlight/lm3630a_bl.c
> > index c63f918..65392f9 100644
> > --- a/drivers/video/backlight/lm3630a_bl.c
> > +++ b/drivers/video/backlight/lm3630a_bl.c
> > @@ -105,7 +105,7 @@ static int lm3630a_chip_init(struct lm3630a_chip *pchip)
> > /* interrupt handling */
> > static void lm3630a_delayed_func(struct work_struct *work)
> > {
> > - unsigned int rval;
> > + int rval;
> > struct lm3630a_chip *pchip;
> >
> > pchip = container_of(work, struct lm3630a_chip, work.work);
> >
>
> There's no drivers/video/backlight/lm3630a_bl.c in v3.12. Which kernel
> is this for?
>
The story is that this driver wasn't submitted to you or to linux-fbdev
but only to lkml.
Andrew Morton (the only person who reads LKML) picked it up in his tree.
Probably at some point he will prod you into taking it through your
tree. Anyway, I resent the patches so they're in -mm now.
regards,
dan carpenter
prev parent reply other threads:[~2013-09-26 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 8:54 [patch 1/2] backlight: lm3630: signedness bug in lm3630a_chip_init() Dan Carpenter
2013-09-25 9:30 ` Jingoo Han
2013-09-25 9:35 ` Dan Carpenter
2013-09-26 9:43 ` Tomi Valkeinen
2013-09-26 9:53 ` Dan Carpenter [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=20130926095344.GA6247@mwanda \
--to=dan.carpenter@oracle.com \
--cc=linux-fbdev@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).