From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] e1000e driver - version 3.3.3
Date: Tue, 26 Jan 2016 03:16:54 -0800 [thread overview]
Message-ID: <1453807014.3113.21.camel@intel.com> (raw)
In-Reply-To: <71843462.40415.1453805333216.JavaMail.zimbra@kwantum.gda.pl>
On Tue, 2016-01-26 at 11:48 +0100, Szymon Tokarski wrote:
> I'm trying to download e1000e-3.3.3.tar.gz driver, but file is
> missing.
>
> I need I219V support.
> Can you fix it?
This is not the right mailing list for this and I have already
responded with the necessary information as well as the correct mailing
list.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20160126/1e701eff/attachment.asc>
prev parent reply other threads:[~2016-01-26 11:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <985715823.40409.1453805224064.JavaMail.zimbra@kwantum.gda.pl>
2016-01-26 10:48 ` [Intel-wired-lan] e1000e driver - version 3.3.3 Szymon Tokarski
2016-01-26 11:16 ` Jeff Kirsher [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=1453807014.3113.21.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=intel-wired-lan@osuosl.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