public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: wk <handygewinnspiel@gmx.de>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org
Subject: Re: POLL: for/against dropping support for kernels < 2.6.22
Date: Wed, 25 Feb 2009 18:58:38 +0100	[thread overview]
Message-ID: <49A586CE.7030600@gmx.de> (raw)
In-Reply-To: <200902221115.01464.hverkuil@xs4all.nl>


> Should we drop support for kernels <2.6.22 in our v4l-dvb repository?
>
> _: Yes
> _: No
>
>   
YES.

> Optional question:
>
> Why:
>   
I assume that the main goal should be development of linux v4l/dvb 
drivers to be included in *new* kernel versions. These dont need compat 
code.
But beside of the main goal there are requirements and other goals

- simplify development and save time (skip)
- keep code as easy as possible (skip)
- having as many testers as needed (don't skip or choose kernel version 
suitable)
- support of linux users who aren't able to update (either dont skip or 
provide backports in regular intervals. still easier to implement)


looking at this it will hurt only users from embedded hardwrae, but at 
least a bunch of them cannot compile modules anyway.
Might be solved by (i.e. yearly) backports.

Would be also interesting which kernel versions are used by list members.

  parent reply	other threads:[~2009-02-25 17:58 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-22 10:15 POLL: for/against dropping support for kernels < 2.6.22 Hans Verkuil
2009-02-22 19:12 ` CityK
2009-02-22 23:52   ` Andy Walls
2009-02-23  4:28     ` [Bulk] " CityK
2009-02-22 22:56 ` Guennadi Liakhovetski
2009-02-22 23:27 ` kilgota
2009-02-23  1:13 ` hermann pitton
2009-02-23  6:41 ` Robert Golding
2009-02-23  8:32 ` VDR User
2009-02-23 12:26 ` Mauro Carvalho Chehab
2009-02-23 14:54   ` Mauro Carvalho Chehab
2009-02-23 14:48 ` Douglas Schilling Landgraf
2009-02-23 14:53 ` David Ellingsworth
2009-02-24  5:04   ` Trent Piepho
2009-02-24  7:25     ` Hans Verkuil
2009-02-24 13:12 ` Ales Jurik
2009-02-24 20:19 ` Hans Verkuil
2009-02-24 20:43   ` Jonathan Johnson
2009-02-25  0:06     ` Markus Rechberger
2009-02-25  3:24       ` Markus Rechberger
2009-02-25  0:01   ` Simeon Simeonov
2009-02-24 20:40 ` Rudy Zijlstra
2009-02-24 21:02 ` Michael Krufky
2009-02-24 23:37   ` hermann pitton
2009-02-25  0:52 ` Ant
2009-02-25  8:23 ` Simon Kenyon
2009-02-25 12:31   ` Simon Kenyon
2009-02-25 17:58 ` wk [this message]
2009-02-25 18:19   ` Jean-Francois Moine
2009-02-25 19:10   ` Hans Werner
2009-02-25 19:32 ` Lars Hanisch
2009-02-26  5:26 ` Mike Isely
2009-02-27  2:25 ` Magnus Damm
2009-03-01 19:51 ` Tobias Stoeber
2009-03-01 21:50 ` Adrian Pardini
  -- strict thread matches above, loose matches on Subject: below --
2009-02-23  1:24 sonofzev
2009-02-23 13:49 Jean Delvare
2009-02-23 13:54 ` Trent Piepho
2009-02-24 11:56 ` John Pilkington
2009-02-24 20:41   ` Simon Kenyon
     [not found] ` <49A3DDFC.6010608@tesco.net>
2009-02-24 13:15   ` Jean Delvare
2009-02-24 14:34     ` John Pilkington
2009-02-23 14:09 Hans Verkuil
2009-02-25  8:35 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=49A586CE.7030600@gmx.de \
    --to=handygewinnspiel@gmx.de \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox