From: Jiri Benc <jbenc@redhat.com>
To: netdev@vger.kernel.org
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Shannon Nelson <shannon.nelson@intel.com>,
Carolyn Wyborny <carolyn.wyborny@intel.com>,
Don Skidmore <donald.c.skidmore@intel.com>,
Bruce Allan <bruce.w.allan@intel.com>,
John Ronciak <john.ronciak@intel.com>,
Mitch Williams <mitch.a.williams@intel.com>
Subject: Re: [PATCH net-next] net: intel: remove dead links
Date: Tue, 5 Apr 2016 16:44:26 +0200 [thread overview]
Message-ID: <20160405164426.4e0d442d@griffin> (raw)
In-Reply-To: <3c9f8ea384ba033f83ec360eef17732ff0a5a8dd.1459866280.git.jbenc@redhat.com>
[removing intel-wired-lan@lists.osuosl.org as I have no interest in the
annoying "awaits moderator approval" emails]
On Tue, 5 Apr 2016 16:25:07 +0200, Jiri Benc wrote:
> The Kconfig for Intel NICs references two different URLs for the "Adapter
> & Driver ID Guide". Neither of those two links works. The current URL seems
> to be
> http://www.intel.com/content/www/us/en/support/network-and-i-o/ethernet-products/000005584.html
> but given it's apparently constantly changing, there's no point in having it
> in the help text.
>
> Just keep a generic pointer to http://support.intel.com. Hopefully, this one
> will have a longer live. It still works, at least.
>
> Futhermore, remove a link to "the latest Intel PRO/100 network driver for
> Linux", this has no place in the mainline kernel and the latest Linux driver
> it offers is from 2006, anyway.
The patch also applies to net. It's probably better to apply it there
than to net-next.
Jiri
next prev parent reply other threads:[~2016-04-05 14:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 14:25 [Intel-wired-lan] [PATCH net-next] net: intel: remove dead links Jiri Benc
2016-04-05 14:25 ` Jiri Benc
2016-04-05 14:44 ` Jiri Benc [this message]
2016-04-06 20:54 ` [Intel-wired-lan] " David Miller
2016-04-06 20:54 ` David Miller
2016-04-06 22:08 ` [Intel-wired-lan] " Jeff Kirsher
2016-04-06 22:08 ` Jeff Kirsher
2016-04-07 2:31 ` [Intel-wired-lan] " Brown, Aaron F
2016-04-07 2:31 ` Brown, Aaron F
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=20160405164426.4e0d442d@griffin \
--to=jbenc@redhat.com \
--cc=bruce.w.allan@intel.com \
--cc=carolyn.wyborny@intel.com \
--cc=donald.c.skidmore@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=mitch.a.williams@intel.com \
--cc=netdev@vger.kernel.org \
--cc=shannon.nelson@intel.com \
/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.