From: Douglas Schilling Landgraf <dougsland@gmail.com>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: v4l <video4linux-list@redhat.com>
Subject: Re: RFC: drop support for kernels < 2.6.22
Date: Thu, 27 Nov 2008 12:22:49 -0200 [thread overview]
Message-ID: <20081127122249.7063d255@gmail.com> (raw)
In-Reply-To: <20081127074139.25d2c576@pedra.chehab.org>
Hello,
On Thu, 27 Nov 2008 07:41:39 -0200
Mauro Carvalho Chehab <mchehab@infradead.org> wrote:
> On Thu, 27 Nov 2008 08:32:22 +0100
> Hans Verkuil <hverkuil@xs4all.nl> wrote:
>
> > Hi all,
> >
> > It been my opinion for quite some time now that we are too generous
> > in the number of kernel versions we support. I think that the
> > benefits no longer outweight the effort we have to put in.
> >
> > This is true in particular for the i2c support since that changed a
> > lot over time. Kernel 2.6.22 is a major milestone for that since it
> > introduced the new-style i2c API.
>
> I prefer to keep backward compat with older kernels. Enterprise
> distros like RHEL is shipped with older kernels (for example RHEL5
> uses kernel 2.6.18). We should support those kernels.
Agreed. I'm using 2.6.18 kernel on some of my machines.
Cheers,
Douglas
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-11-27 14:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-27 7:32 RFC: drop support for kernels < 2.6.22 Hans Verkuil
2008-11-27 9:41 ` Mauro Carvalho Chehab
2008-11-27 14:22 ` Douglas Schilling Landgraf [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-27 10:23 Hans Verkuil
2008-11-27 13:52 ` Andy Walls
2008-11-27 15:54 ` Jackson Yee
2008-11-27 14:08 ` Mauro Carvalho Chehab
2008-11-27 14:20 ` Laurent Pinchart
2008-11-28 10:10 ` Darren Longhorn
2008-11-27 14:18 Hans Verkuil
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=20081127122249.7063d255@gmail.com \
--to=dougsland@gmail.com \
--cc=mchehab@infradead.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 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.