> Was hoping 2.6.17 would be out within one week, doesn't look like it
> is going to happen.
> My thesis defense is coming up, need to merge my patches against some kernel
> (requiring 2.6.16.1 looks weird).
>
Surprisingly I'm in the same position ^_^ Basing my patches on 2.6.16 makes
a lot of changes produce compiler warnings again (e.g. due to changed
prototypes in ipt_* matches and targets).
> On a machine that 2.6.16.1 runs bug-free, is it sane to assume
> 2.6.17-rc3 will as well?
> If it fails outright, I can revert, but if it is unstable I'm going to
> have some problems.
> (You would be surprised how long it took me to discover a mistake that
> sys_rename(on any filesystem) -> deadlock with my custom patch).
If it is a kernel problem, report it. If it is a problem of your patch,
well, I suppose you need to fix it then. :/
Jan Engelhardt
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]