On Monday, October 11, 2010, Justin P. Mattock wrote:
> On 10/10/2010 12:41 PM, Rafael J. Wysocki wrote:
> > On Sunday, October 10, 2010, Justin P. Mattock wrote:
> >>On 10/10/2010 10:51 AM, Rafael J. Wysocki wrote:
> >>> This message has been generated automatically as a part of a summary
>
On 10/10/2010 12:41 PM, Rafael J. Wysocki wrote:
On Sunday, October 10, 2010, Justin P. Mattock wrote:
On 10/10/2010 10:51 AM, Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the curre
On Sunday, October 10, 2010, Mikael Pettersson wrote:
> On Sun, 10 Oct 2010 19:51:49 +0200 (CEST), "Rafael J. Wysocki"
> wrote:
> > The following bug entry is on the current list of known regressions
> > from 2.6.35. Please verify if it still should be listed and let the
> > tracking team
> > k
On Sun, 10 Oct 2010 19:51:49 +0200 (CEST), "Rafael J. Wysocki"
wrote:
> The following bug entry is on the current list of known regressions
> from 2.6.35. Please verify if it still should be listed and let the tracking
> team
> know (either way).
>
>
> Bug-Entry : http://bugzilla.kernel.o
On 10/10/2010 12:41 PM, Rafael J. Wysocki wrote:
On Sunday, October 10, 2010, Justin P. Mattock wrote:
On 10/10/2010 10:51 AM, Rafael J. Wysocki wrote:
This message has been generated automatically as a part of a summary report
of recent regressions.
The following bug entry is on the curre
On Sunday, October 10, 2010, Justin P. Mattock wrote:
> On 10/10/2010 10:51 AM, Rafael J. Wysocki wrote:
> > 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
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. 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.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. Please verify if it still should
be listed and let the tracking team k
On 10/10/2010 10:51 AM, Rafael J. Wysocki wrote:
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 2.6.35. Please verify if it still should be listed and let the tracking
This message has been generated automatically as a part of a report
of regressions introduced between 2.6.34 and 2.6.35.
The following bug entry is on the current list of known regressions
introduced between 2.6.34 and 2.6.35. Please verify if it still should
be listed and let the tracking team k
This message contains a list of some post-2.6.34 regressions introduced before
2.6.35, 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-2.6.34 regressions, please let us kno
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 2.6.35. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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 2.6.35. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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 2.6.35. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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 2.6.35. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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 2.6.35. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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 2.6.35. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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 2.6.35. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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 2.6.35. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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 2.6.35. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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 2.6.35. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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 2.6.35. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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 2.6.35. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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 2.6.35. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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 2.6.35. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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 2.6.35. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
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 2.6.35. Please verify if it still should be listed and let the tracking
team
know (either way).
Bug-Entry : http://b
This message contains a list of some regressions from 2.6.35,
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 2.6.35, please let us
know either and we'll add th
48 matches
Mail list logo