All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
	Luis de Bethencourt <luis@debethencourt.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: divide error: 0000 in the gspca_topro
Date: Tue, 10 Feb 2015 09:28:58 +0100	[thread overview]
Message-ID: <54D9C14A.1080906@redhat.com> (raw)
In-Reply-To: <20150209135656.11cc85e6@recife.lan>

Hi,

On 09-02-15 16:56, Mauro Carvalho Chehab wrote:
> Em Mon, 09 Feb 2015 10:23:48 +0000
> Luis de Bethencourt <luis@debethencourt.com> escreveu:
>
>> On Sun, Feb 08, 2015 at 06:07:45PM -0800, Linus Torvalds wrote:
>>> I got this, and it certainly seems relevant,.
>>>
>>> It would seem that that whole 'quality' thing needs some range
>>> checking, it should presumably be in the range [1..100] in order to
>>> avoid negative 'sc' values or the divide-by-zero.
>>>
>>> Hans, Mauro?
>>>
>>>                        Linus
>>
>> Hello Linus,
>>
>> The case of quality being set to 0 is correctly handled in
>> drivers/media/usb/gspca/jpeg.h [0], so I have sent a patch to do the same
>> in topro.c.
>
> Patch looks good to me.
>
> I'll double check if some other driver has the same bad handling for
> quality set and give a couple days for Hans to take a look.
>
> If he's fine with this approach, I'll add it on a separate pull request.

Luis' patch for this looks good to me and is:

Acked-by: Hans de Goede <hdegoede@redhat.com>

Mauro, thanks for picking this one up.

Regards,

Hans

      parent reply	other threads:[~2015-02-10  8:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <54D7E0B8.30503@reflexion.tv>
2015-02-09  2:07 ` Fwd: divide error: 0000 in the gspca_topro Linus Torvalds
2015-02-09 10:23   ` Luis de Bethencourt
2015-02-09 15:56     ` Mauro Carvalho Chehab
2015-02-09 16:06       ` Luis de Bethencourt
2015-02-10  8:28       ` Hans de Goede [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=54D9C14A.1080906@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=linux-media@vger.kernel.org \
    --cc=luis@debethencourt.com \
    --cc=mchehab@osg.samsung.com \
    --cc=torvalds@linux-foundation.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 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.