On Thu, Feb 21, 2008 at 01:30:37PM -0800, Greg KH wrote:I don't see any way for getting a proof in any direction, but no matter how many SOB lines a patch has my impression is that usually at a maximum the one person who applies a patch reviews it ("review" as in "understands the code in question well and reviews the patch line for line"). Sometimes there's even simply noone who could a patch at all, e.g. I'm not sure whether there is anyone at all who would be able to review a patch by Sam fiddling with kbuild internals. How many lines of code get changed in the kernel per day? And we should have for each changed line two people who are both experienced enough in this area of the kernel and who have the time to review this line? Even one of our best maintained subsystems has commits that contain bugs like + if ((!tid_agg_rx->reorder_buf) && net_ratelimit()) { + printk(KERN_ERR "can not allocate reordering buffer " + "to tid %d\n", tid); + goto end; + } 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 --
| Max Krasnyansky | Re: Inquiry: Should we remove "isolcpus= kernel boot option? (may have realtime us... |
| Jeremy Allison | Re: [RFC] Heads up on sys_fallocate() |
| Randy Dunlap | Re: -mm merge plans for 2.6.23 (pcmcia) |
| Damien Wyart | ACPI power off regression in 2.6.23-rc8 (NOT in rc7) |
git: | |
| Josip Rodin | Re: bnx2_poll panicking kernel |
| Linus Torvalds | Re: [GIT]: Networking |
| Denys Fedoryshchenko | thousands of classes, e1000 TX unit hang |
