From: Hans Verkuil <hverkuil@xs4all.nl>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: Laurent Pinchart <laurent.pinchart@skynet.be>,
video4linux-list@redhat.com,
"v4l-dvb maintainer list" <v4l-dvb-maintainer@linuxtv.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
linux-kernel@vger.kernel.org,
davinci-linux-open-source-bounces@linux.davincidsp.com
Subject: Re: [PULL] http://www.linuxtv.org/hg/~hverkuil/v4l-dvb-ng
Date: Tue, 2 Dec 2008 18:26:08 +0100 [thread overview]
Message-ID: <200812021826.09133.hverkuil@xs4all.nl> (raw)
In-Reply-To: <20081202152100.0a4dd2c1@pedra.chehab.org>
On Tuesday 02 December 2008 18:21:00 Mauro Carvalho Chehab wrote:
> On Tue, 2 Dec 2008 17:58:35 +0100
>
> Laurent Pinchart <laurent.pinchart@skynet.be> wrote:
> > > Are you meaning marking this as experimental at Kconfig? This
> > > seems too complex, since we'll need to test for some var on every
> > > driver that were converted, providing two KABI options for each
> > > converted driver (the legacy and the v4l2_device way). This
> > > doesn't seem to be a good idea, since will add a lot of extra
> > > complexity to debug bugs.
> >
> > Not at the Kconfig level, just in the documentation (and possible
> > headers).
>
> Ah, ok. Good point.
>
> > This is a work in progress. Hans wants the changes to go mainline
> > to get broader testing, which is a valid reason, but I'd like to
> > make sure people understand that more changes are coming.
>
> Maybe instead we should have a TODO list somewhere with the
> programmed changes, especially at the subsystem core.
Sure, I can add some comments outlining future developments in
v4l2-device.h and v4l2-subdev.h. The v4l2-framework document can point
to those headers (headers are easier to keep in sync when new features
arrive than documentation).
But I'll wait with this until I get Mauro's review back, just in case
there are more changes for me to do.
Regards,
Hans
--
Hans Verkuil - video4linux developer - sponsored by TANDBERG
next prev parent reply other threads:[~2008-12-02 17:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 11:46 Hans Verkuil
2008-12-01 12:27 ` Mauro Carvalho Chehab
2008-12-01 12:31 ` Hans Verkuil
2008-12-01 12:31 ` Laurent Pinchart
2008-12-01 12:51 ` Hans Verkuil
2008-12-01 13:29 ` Laurent Pinchart
2008-12-01 13:45 ` Hans Verkuil
2008-12-01 14:24 ` Laurent Pinchart
2008-12-01 14:47 ` Hans Verkuil
2008-12-02 17:01 ` Laurent Pinchart
2008-12-01 15:06 ` Mauro Carvalho Chehab
2008-12-01 18:07 ` Hans Verkuil
2008-12-02 16:58 ` Laurent Pinchart
2008-12-02 17:21 ` Mauro Carvalho Chehab
2008-12-02 17:26 ` Hans Verkuil [this message]
2008-12-02 0:02 ` Andy Walls
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=200812021826.09133.hverkuil@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=davinci-linux-open-source-bounces@linux.davincidsp.com \
--cc=laurent.pinchart@skynet.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=v4l-dvb-maintainer@linuxtv.org \
--cc=video4linux-list@redhat.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®