Messages in this thread | | | Date | Sun, 24 Sep 2006 00:47:40 +0200 | From | Adrian Bunk <> | Subject | Re: Linux 2.6.16.30-pre1 |
| |
On Sat, Sep 23, 2006 at 11:20:54PM +0200, Jean Delvare wrote: > Hi Lee, > > > On Sat, 2006-09-23 at 22:49 +0200, Jean Delvare wrote: > > > I will not use 2.6.16.y with its current rules, for sure, and I doubt > > > any distribution will. Wasn't the whole point of 2.6.16.y to serve as > > > a common base between several distributions? > > > > I would not expect distros to be interested in a 2.6 tree that does not > > add support for new devices. Isn't new hardware support one of the main > > areas where distros routinely get ahead of mainline? > > It really depends on the distribution, and even more of the specific > product. I know for a fact that Suse has no interest in supporting > additional hardware in the saa7134 driver for SLES10, for example. I > suspect that distributions only backport hardware support when a > customer asks for it, and they have some in-house knowledge to do it > safely.
[ see my comment about distributions in the other email ]
And I'd expect distributions with some in-house knowledge to do at most cherry picking from my tree.
> My original understanding was that 2.6.16.y was meant to be a common > tree between different distributions and products, containing only the > unquestionable fixes - i.e. security, data corruption and other oopses, > in the -stable spirit - and then different distributions would add their > own patches on top of it as they see fit.
How do you define "unquestionable fixes"?
E.g. what if a distribution supports an external module, and a fix requires changing the kernel ABI this module uses?
The users of my trees are mostly people using self-compiled kernels that want security fixes but no regressions.
> Jean Delvare
cu Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |