From: Jens Axboe <axboe@suse.de>
To: "Ronciak, John" <john.ronciak@intel.com>
Cc: netdev@vger.kernel.org, "Brandeburg,
Jesse" <jesse.brandeburg@intel.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>
Subject: Re: e1000 Invalid truesize
Date: Wed, 26 Apr 2006 19:58:53 +0200 [thread overview]
Message-ID: <20060426175853.GF5002@suse.de> (raw)
In-Reply-To: <F50A4280B6033741B1DD2B4E902258B13F4EAD@orsmsx411.amr.corp.intel.com>
On Wed, Apr 26 2006, Ronciak, John wrote:
> Please follow what has been happening on netdev. Dave Miller added this
> BUG to 2.6.17-rc as something we (Intel LAD) pointed out to them. Jeff
> Garzik has, as of this morning, queued our e1000 patch for this. He's
> been a little behind.
Ah ok, I guess I should have searched there first. I was just grasping
at straws, hoping perhaps some new debug aid exposed my e1000 problem
and it finally could get fixed.
> If you want to know more about the problem, please read the entire
> netdev discussion about this.
Thanks.
--
Jens Axboe
prev parent reply other threads:[~2006-04-26 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 15:24 e1000 Invalid truesize Ronciak, John
2006-04-26 17:58 ` Jens Axboe [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=20060426175853.GF5002@suse.de \
--to=axboe@suse.de \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=netdev@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.