This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 3.2. Please verify if it still should be listed and let the tracking team
know (either way).
Bug-Entry :
This message contains a list of some regressions from 3.2,
for which there are no fixes in the mainline known to the tracking team.
If any of them have been fixed already, please let us know.
If you know of any other unresolved regressions from 3.2, please let us
know either and we'll add them to
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 3.2. Please verify if it still should be listed and let the tracking team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 3.2. Please verify if it still should be listed and let the tracking team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 3.2. Please verify if it still should be listed and let the tracking team
know (either way).
Bug-Entry :
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the current list of known regressions
from 3.2. Please verify if it still should be listed and let the tracking team
know (either way).
Bug-Entry :
This message contains a list of some post-3.1 regressions introduced before
3.2, for which there are no fixes in the mainline known to the tracking team.
If any of them have been fixed already, please let us know.
If you know of any other unresolved post-3.1 regressions, please let us know
either
This message has been generated automatically as a part of a report
of regressions introduced between 3.1 and 3.2.
The following bug entry is on the current list of known regressions
introduced between 3.1 and 3.2. Please verify if it still should
be listed and let the tracking team know (either
This message has been generated automatically as a part of a report
of regressions introduced between 3.1 and 3.2.
The following bug entry is on the current list of known regressions
introduced between 3.1 and 3.2. Please verify if it still should
be listed and let the tracking team know (either
This message has been generated automatically as a part of a report
of regressions introduced between 3.1 and 3.2.
The following bug entry is on the current list of known regressions
introduced between 3.1 and 3.2. Please verify if it still should
be listed and let the tracking team know (either
This message has been generated automatically as a part of a report
of regressions introduced between 3.1 and 3.2.
The following bug entry is on the current list of known regressions
introduced between 3.1 and 3.2. Please verify if it still should
be listed and let the tracking team know (either
This message has been generated automatically as a part of a report
of regressions introduced between 3.1 and 3.2.
The following bug entry is on the current list of known regressions
introduced between 3.1 and 3.2. Please verify if it still should
be listed and let the tracking team know (either
This message has been generated automatically as a part of a report
of regressions introduced between 3.1 and 3.2.
The following bug entry is on the current list of known regressions
introduced between 3.1 and 3.2. Please verify if it still should
be listed and let the tracking team know (either
On 12/03/2012, at 10:31 AM, Rafael J. Wysocki wrote:
Bug-Entry : https://bugzilla.kernel.org/show_bug.cgi?id=42821
Subject : alpha: futex regression bisected
Submitter : Michael Cree mc...@orcon.net.nz
Date: 2012-02-20 8:20 (21 days old)
First-Bad-Commit:
no change still not upstream
On Sun, Mar 11, 2012 at 2:46 PM, Rafael J. Wysocki r...@sisk.pl wrote:
This message has been generated automatically as a part of a report
of regressions introduced between 3.1 and 3.2.
The following bug entry is on the current list of known regressions
15 matches
Mail list logo
