From: Trent Piepho <xyzzy@speakeasy.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-dvb-maintainer@linuxtv.org, akpm@osdl.org,
Linux and Kernel Video <video4linux-list@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [v4l-dvb-maintainer] Re: [PATCH 00/23] V4L/DVB fixes
Date: Sun, 30 Jul 2006 00:11:13 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0607292352490.32415@shell2.speakeasy.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0607292300070.4168@g5.osdl.org>
On Sat, 29 Jul 2006, Linus Torvalds wrote:
> On Sat, 29 Jul 2006, Mauro Carvalho Chehab wrote:
> >
> > Please pull these (and the other ones) from master branch at:
> > kernel.org:/pub/scm/linux/kernel/git/mchehab/v4l-dvb.git
>
> I get a _huge_ diffstat with
>
> 135 files changed, 3056 insertions(+), 1562 deletions(-)
There are mostly two things which did this.
One is that Mauro translated almost all of the V4L1 radio card drivers to
V4L2. The changes are all very repetitive, but it made a huge diffstat:
15 files changed, 1758 insertions(+), 918 deletions(-)
The second source is the dvb_attach() system, which was not supposed to go
in 2.6.18, it was for 2.6.19.
74 files changed, 827 insertions(+), 622 deletions(-)
The dvb_attach() stuff isn't ready for 2.6.18, it hasn't been tested at all
and it's a very significant change. The ISA radio card drivers.... I
don't think they are used very much anymore.
next prev parent reply other threads:[~2006-07-30 7:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 18:03 mchehab
2006-07-25 22:41 ` Edgar Toernig
2006-07-25 23:10 ` [v4l-dvb-maintainer] " Michael Krufky
2006-07-26 1:00 ` Trent Piepho
2006-07-26 7:49 ` Edgar Toernig
2006-07-26 9:11 ` Alan Cox
2006-07-30 1:25 ` Mauro Carvalho Chehab
2006-07-30 6:02 ` Linus Torvalds
2006-07-30 7:11 ` Trent Piepho [this message]
2006-07-30 11:53 ` [v4l-dvb-maintainer] " Mauro Carvalho Chehab
2006-07-30 12:07 ` Mauro Carvalho Chehab
2006-07-30 17:56 ` Alan Cox
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=Pine.LNX.4.58.0607292352490.32415@shell2.speakeasy.net \
--to=xyzzy@speakeasy.org \
--cc=akpm@osdl.org \
--cc=linux-dvb-maintainer@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=torvalds@osdl.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®