From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org,
Mats Randgaard <mats.randgaard@tandberg.com>
Subject: Re: [GIT PATCHES FOR 2.6.37] davinci & videobuf fixes
Date: Wed, 22 Sep 2010 15:39:03 -0300 [thread overview]
Message-ID: <4C9A4D47.3080605@redhat.com> (raw)
In-Reply-To: <201009071123.25174.hverkuil@xs4all.nl>
Em 07-09-2010 06:23, Hans Verkuil escreveu:
> Hi Mauro,
>
> The following changes since commit 50b9d21ae2ac1b85be46f1ee5aa1b5e588622361:
> Jarod Wilson (1):
> V4L/DVB: mceusb: add two new ASUS device IDs
>
> are available in the git repository at:
>
> ssh://linuxtv.org/git/hverkuil/v4l-dvb.git for-2.6.37
>
> Hans Verkuil (1):
> videobuf-dma-sg: set correct size in last sg element
Ok.
>
> Mats Randgaard (5):
> videobuf-core.c: Replaced BUG_ON with WARN_ON
Why? Please provide a description to allow us to understand why this change makes sense.
Is there any condition where this would be acceptable?
> vpif_cap/disp: Removed section mismatch warning
> vpif_cap/disp: Replaced kmalloc with kzalloc
> vpif_cap: don't ignore return code of videobuf_poll_stream()
The better would be to provide some description for all patches, but, in this
specific case, they're trivial.
Applied, thanks.
> vpif_cap/disp: Fixed strlcpy NULL pointer bug
Hmm... this one doesn't make sense to me. Instead, you should be sure that
config->card_name (or cap->card) is always filled.
Ok, I've applied 4 of the 6 patches (I've included the patch of the last email
on the above).
Please, provide a better solution for the strlcpy NULL pointer bug, properly
filling the config struct in all cases.
Cheers,
Mauro
next parent reply other threads:[~2010-09-22 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201009071123.25174.hverkuil@xs4all.nl>
2010-09-22 18:39 ` Mauro Carvalho Chehab [this message]
2010-09-22 18:49 ` [GIT PATCHES FOR 2.6.37] davinci & videobuf fixes Hans Verkuil
2010-09-22 19:49 ` Mauro Carvalho Chehab
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=4C9A4D47.3080605@redhat.com \
--to=mchehab@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mats.randgaard@tandberg.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 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.