This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
On Fri, 23 Jul 2010 14:15:51 +0200 (CEST)
"Rafael J. Wysocki" wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.33 and 2.6.34.
>
> The following bug entry is on the current list of known regressions
> introduced between 2.6.33 an
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.33 and 2.6.34.
The following bug entry is on the current list of known regressions
introduced between 2.6.33 and 2.6.34. Please verify if it still should
be listed and let the tracking team k
