On Thu, Jan 31, 2013 at 05:43:51PM -0600, Michael Roth wrote:
This reverts commit 84dd2120247a7d25ff1bb337de21c0e76816ad2d.
I'm not sure what issue the original commit was meant to fix, or if
the logic is actually wrong, but it causes e1000 to stop working
after a guest issues a reset.
On Thu, Jan 31, 2013 at 05:43:51PM -0600, Michael Roth wrote:
This reverts commit 84dd2120247a7d25ff1bb337de21c0e76816ad2d.
I'm not sure what issue the original commit was meant to fix, or if
the logic is actually wrong, but it causes e1000 to stop working
after a guest issues a reset.
Applied. Thanks.
Regards,
Anthony Liguori
On Fri, Feb 01, 2013 at 03:20:59PM +0800, Amos Kong wrote:
On Thu, Jan 31, 2013 at 05:43:51PM -0600, Michael Roth wrote:
This reverts commit 84dd2120247a7d25ff1bb337de21c0e76816ad2d.
I'm not sure what issue the original commit was meant to fix, or if
the logic is actually wrong, but it
On Fri, Feb 01, 2013 at 03:53:22PM +0800, Amos Kong wrote:
On Fri, Feb 01, 2013 at 03:20:59PM +0800, Amos Kong wrote:
On Thu, Jan 31, 2013 at 05:43:51PM -0600, Michael Roth wrote:
This reverts commit 84dd2120247a7d25ff1bb337de21c0e76816ad2d.
I'm not sure what issue the original commit
Michael Roth mdr...@linux.vnet.ibm.com writes:
This reverts commit 84dd2120247a7d25ff1bb337de21c0e76816ad2d.
I'm not sure what issue the original commit was meant to fix, or if
the logic is actually wrong, but it causes e1000 to stop working
after a guest issues a reset.
From what I can
On Fri, Feb 01, 2013 at 08:49:00AM -0600, mdroth wrote:
On Fri, Feb 01, 2013 at 03:53:22PM +0800, Amos Kong wrote:
On Fri, Feb 01, 2013 at 03:20:59PM +0800, Amos Kong wrote:
On Thu, Jan 31, 2013 at 05:43:51PM -0600, Michael Roth wrote:
This reverts commit
On Fri, Feb 01, 2013 at 08:29:48AM -0600, mdroth wrote:
On Fri, Feb 01, 2013 at 03:20:59PM +0800, Amos Kong wrote:
On Thu, Jan 31, 2013 at 05:43:51PM -0600, Michael Roth wrote:
This reverts commit 84dd2120247a7d25ff1bb337de21c0e76816ad2d.
I'm not sure what issue the original commit
This reverts commit 84dd2120247a7d25ff1bb337de21c0e76816ad2d.
I'm not sure what issue the original commit was meant to fix, or if
the logic is actually wrong, but it causes e1000 to stop working
after a guest issues a reset.
From what I can tell a guest with an e1000 nic has no way of changing
On Thu, Jan 31, 2013 at 05:43:51PM -0600, Michael Roth wrote:
This reverts commit 84dd2120247a7d25ff1bb337de21c0e76816ad2d.
I'm not sure what issue the original commit was meant to fix, or if
the logic is actually wrong, but it causes e1000 to stop working
after a guest issues a reset.
Hi
On Fri, Feb 01, 2013 at 03:20:59PM +0800, Amos Kong wrote:
On Thu, Jan 31, 2013 at 05:43:51PM -0600, Michael Roth wrote:
This reverts commit 84dd2120247a7d25ff1bb337de21c0e76816ad2d.
I'm not sure what issue the original commit was meant to fix, or if
the logic is actually wrong, but it
11 matches
Mail list logo