From: Daniel Borkmann <dborkman@redhat.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>
Subject: Re: kmemleak through e1000?
Date: Wed, 05 Mar 2014 09:23:22 +0100 [thread overview]
Message-ID: <5316DEFA.8060600@redhat.com> (raw)
In-Reply-To: <CAErSpo54aGGbqGG08bOWCor3xp5r=kxOXm0wp27Lyhr5=qJRGA@mail.gmail.com>
On 03/04/2014 11:49 PM, Bjorn Helgaas wrote:
...
> Thanks, Daniel. I confirmed that the two MSI fixes are not in the
> tree you're testing, so that's probably what you're seeing.
Ok, that's great, thanks a lot for the clarification Bjorn.
prev parent reply other threads:[~2014-03-05 8:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 15:55 kmemleak through e1000? Daniel Borkmann
2014-03-04 20:58 ` Bjorn Helgaas
2014-03-04 21:11 ` [E1000-devel] " Nelson, Shannon
2014-03-04 21:33 ` Bjorn Helgaas
2014-03-04 21:55 ` Daniel Borkmann
2014-03-04 22:49 ` Bjorn Helgaas
2014-03-05 8:23 ` Daniel Borkmann [this message]
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=5316DEFA.8060600@redhat.com \
--to=dborkman@redhat.com \
--cc=bhelgaas@google.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=linux-pci@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).