On Tue, 10 May 2011 16:35:40 -0700
Noah Meyerhans no...@debian.org wrote:
On Tue, May 10, 2011 at 03:11:00PM -0700, Stephen Hemminger wrote:
There were two more follow on commits in stable related to this.
I recommend merging 2.6.38.6 which includes these.
The problem still exists in the
From: Noah Meyerhans no...@debian.org
Date: Tue, 10 May 2011 16:35:40 -0700
On Tue, May 10, 2011 at 03:11:00PM -0700, Stephen Hemminger wrote:
There were two more follow on commits in stable related to this.
I recommend merging 2.6.38.6 which includes these.
The problem still exists in the
On Thu, 12 May 2011 15:59:16 -0700 (PDT)
David Miller da...@davemloft.net wrote:
From: Noah Meyerhans no...@debian.org
Date: Tue, 10 May 2011 16:35:40 -0700
On Tue, May 10, 2011 at 03:11:00PM -0700, Stephen Hemminger wrote:
There were two more follow on commits in stable related to this.
On Tue, 10 May 2011 16:35:40 -0700
Noah Meyerhans no...@debian.org wrote:
On Tue, May 10, 2011 at 03:11:00PM -0700, Stephen Hemminger wrote:
There were two more follow on commits in stable related to this.
I recommend merging 2.6.38.6 which includes these.
The problem still exists in the
On Thu, May 12, 2011 at 04:43:22PM -0700, Stephen Hemminger wrote:
There were two more follow on commits in stable related to this.
I recommend merging 2.6.38.6 which includes these.
The problem still exists in the current 2.6.38.6. Backing out 5f1c356a
still solves the problem
On Tue, 10 May 2011 11:05:40 -0700
Noah Meyerhans no...@debian.org wrote:
On Tue, May 10, 2011 at 01:42:49PM +0100, Ben Hutchings wrote:
This is pretty weird. Debian version 2.6.38-3 has a few bridging
changes from stable 2.6.38.3 and 2.6.38.4, but they don't look like they
would
On Tue, May 10, 2011 at 03:11:00PM -0700, Stephen Hemminger wrote:
There were two more follow on commits in stable related to this.
I recommend merging 2.6.38.6 which includes these.
The problem still exists in the current 2.6.38.6. Backing out 5f1c356a
still solves the problem there.
I have
7 matches
Mail list logo
