Prev: 2.6.35-rc4-git3: Reported regressions from 2.6.34
Next: linux-next: build failure after merge of the infiniband tree
From: Jiri Slaby on 29 Jul 2010 16:40
On 07/23/2010 10:05 PM, Rafael J. Wysocki wrote:
> On Friday, July 23, 2010, Kees Cook wrote:
>> On Fri, Jul 23, 2010 at 01:47:30PM +0200, 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.34. Please verify if it still should be listed and let the tracking team
>>> know (either way).
>>
>> The regression still exists[1] in the mainline kernel -- the confirmed fix
>> mentioned below has not been committed.
>
> That's why the bug entry hasn't been closed yet. :-)

Finally, it's merged as e7b96f28c...

regards,
--
js
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
First  |  Prev  | 
Pages: 1 2
Prev: 2.6.35-rc4-git3: Reported regressions from 2.6.34
Next: linux-next: build failure after merge of the infiniband tree