On Thu, Apr 26, 2007 at 02:46:08AM -0400, Daniel Barkalow wrote:
>
> On Thu, 26 Apr 2007, Adrian Bunk wrote:
>
> > Number of different known regressions compared to 2.6.20 at the time
> > of the 2.6.21 release:
> > 14
>
> I count 13. (v2) had 15 items, of which 2 were subsequently fixed or found
> to be inapplicable.
Plus one that has been reported since my last list.
> > Number of different known regressions compared to 2.6.20 at the time
> > of the 2.6.21 release with patches available at the time of the 2.6.21
> > release [1]:
> > 3
>
> The -stable team can presumably take care of these in 2.6.21.1, right?
Two of them are heavily discussed patches, and I'm therefore not sure
they will ever reach the 2.6.21 branch now that the attention has been
shifted away from 2.6.21 regressions.
> That leaves 10 that need developer attention.
>
> John Stultz seems to be taking care of 3 of them.
>
> Oliver Neukum has 1.
>
> 2 are particular drivers (ali_pata and rtl8139, according to the
> reports).
>
> 2 seem to be ACPI-related; at least one has a candidate patch now.
>
> 1 seems to be an ALSA problem.
>
> 1 is STD and being debugged.
You are overinterpreting the Handled-By field in my reports.
It does not imply that this person promised to fix this issue, it only
says that this person is or was working on this issue.
And more than 50% of the issues were reported first last month or
earlier and are still unfixed despite repeated reminder emails - if
they weren't fixed until now they might as well become similar to
"foo seems to be broken since at about 2.6.9" issues.
It sounds highly unrealistic that all issues unfixed for a month
suddenly become fixed even though the main focus of everyone shifts to
2.6.21.
> It looks like all of the known regressions are being worked on, and
> getting fixes in for them is -stable material at this point. Furthermore,
> it doesn't look to me like anyone who is needed for dealing with these
> regressions is trying to get stuff into the 2.6.22 merge window.
>...
That's a wrong impression, nearly every active kernel developer has at
least one patch pending for 2.6.22.
> -Daniel
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 [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]
