From: Richard Davies <richard.davies@elastichosts.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: Dmitry Fleytman <dmitry@daynix.com>,
linux-kernel@vger.kernel.org, e1000-devel@lists.sourceforge.net,
Chris Webb <chris.webb@elastichosts.com>
Subject: Re: [E1000-devel] [PATCH] RX initialization sequence fixed - enable RX after corresponding ring initialization only
Date: Fri, 19 Oct 2012 20:19:44 +0100 [thread overview]
Message-ID: <20121019191944.GA27699@alpha.arachsys.com> (raw)
In-Reply-To: <1350280341.2152.12.camel@jtkirshe-mobl>
Jeff Kirsher wrote:
> Dmitry Fleytman wrote:
> > Reported-by: Chris Webb <chris.webb@elastichosts.com>
> > Reported-by: Richard Davies <richard.davies@elastichosts.com>
> >
> > Signed-off-by: Dmitry Fleytman <dmitry@daynix.com>
> > ---
> > drivers/net/ethernet/intel/e1000/e1000_ethtool.c | 9 +++++----
> > drivers/net/ethernet/intel/e1000/e1000_main.c | 18
> > ++++++++++++++++--
> > 2 files changed, 21 insertions(+), 6 deletions(-)
>
> I will add it to my queue. Thanks!
Hi Jeff,
I hope it was already clear from the following discussion - this patch
turned out to be a qemu-kvm bug and you do not need to apply it.
Dmitry - please confirm.
Richard.
next prev parent reply other threads:[~2012-10-19 19:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-14 17:19 [PATCH] e1000 driver RX race condition fixed Dmitry Fleytman
2012-10-14 17:19 ` [PATCH] RX initialization sequence fixed - enable RX after corresponding ring initialization only Dmitry Fleytman
2012-10-15 5:52 ` [E1000-devel] " Jeff Kirsher
2012-10-15 17:41 ` Dmitry Fleytman
2012-10-19 19:19 ` Richard Davies [this message]
2012-10-19 19:34 ` Dmitry Fleytman
2012-10-23 5:23 ` Jeff Kirsher
2012-10-15 18:53 ` [PATCH] e1000 driver RX race condition fixed Alexander Duyck
2012-10-15 19:44 ` Dmitry Fleytman
2012-10-15 20:03 ` Alexander Duyck
2012-10-15 20:20 ` Dmitry Fleytman
2012-10-15 21:17 ` Alexander Duyck
2012-10-17 17:46 ` Jan Ceuleers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121019191944.GA27699@alpha.arachsys.com \
--to=richard.davies@elastichosts.com \
--cc=chris.webb@elastichosts.com \
--cc=dmitry@daynix.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.