Patch Detail
get:
Show a patch.
patch:
Update a patch.
put:
Update a patch.
GET /api/patches/934752/?format=api
{ "id": 934752, "url": "http://patchwork.ozlabs.org/api/patches/934752/?format=api", "web_url": "http://patchwork.ozlabs.org/project/intel-wired-lan/patch/687412e4b938cdf17baf87b2961a48283edd7480.1530005114.git.mchehab+samsung@kernel.org/", "project": { "id": 46, "url": "http://patchwork.ozlabs.org/api/projects/46/?format=api", "name": "Intel Wired Ethernet development", "link_name": "intel-wired-lan", "list_id": "intel-wired-lan.osuosl.org", "list_email": "intel-wired-lan@osuosl.org", "web_url": "", "scm_url": "", "webscm_url": "", "list_archive_url": "", "list_archive_url_format": "", "commit_url_format": "" }, "msgid": "<687412e4b938cdf17baf87b2961a48283edd7480.1530005114.git.mchehab+samsung@kernel.org>", "list_archive_url": null, "date": "2018-06-26T09:49:10", "name": "[8/9] networking: e1000.rst: Get rid of Sphinx warnings", "commit_ref": null, "pull_url": null, "state": "accepted", "archived": false, "hash": "6aa045bc632d78a452955fcabb8c6a95e65f4949", "submitter": { "id": 73965, "url": "http://patchwork.ozlabs.org/api/people/73965/?format=api", "name": "Mauro Carvalho Chehab", "email": "mchehab+samsung@kernel.org" }, "delegate": { "id": 68, "url": "http://patchwork.ozlabs.org/api/users/68/?format=api", "username": "jtkirshe", "first_name": "Jeff", "last_name": "Kirsher", "email": "jeffrey.t.kirsher@intel.com" }, "mbox": "http://patchwork.ozlabs.org/project/intel-wired-lan/patch/687412e4b938cdf17baf87b2961a48283edd7480.1530005114.git.mchehab+samsung@kernel.org/mbox/", "series": [ { "id": 52110, "url": "http://patchwork.ozlabs.org/api/series/52110/?format=api", "web_url": "http://patchwork.ozlabs.org/project/intel-wired-lan/list/?series=52110", "date": "2018-06-26T09:49:09", "name": "Fix references for some missing documentation files", "version": 1, "mbox": "http://patchwork.ozlabs.org/series/52110/mbox/" } ], "comments": "http://patchwork.ozlabs.org/api/patches/934752/comments/", "check": "pending", "checks": "http://patchwork.ozlabs.org/api/patches/934752/checks/", "tags": {}, "related": [], "headers": { "Return-Path": "<intel-wired-lan-bounces@osuosl.org>", "X-Original-To": [ "incoming@patchwork.ozlabs.org", "intel-wired-lan@lists.osuosl.org" ], "Delivered-To": [ "patchwork-incoming@bilbo.ozlabs.org", "intel-wired-lan@lists.osuosl.org" ], "Authentication-Results": [ "ozlabs.org;\n\tspf=pass (mailfrom) smtp.mailfrom=osuosl.org\n\t(client-ip=140.211.166.133; helo=hemlock.osuosl.org;\n\tenvelope-from=intel-wired-lan-bounces@osuosl.org;\n\treceiver=<UNKNOWN>)", "ozlabs.org;\n\tdmarc=fail (p=none dis=none) header.from=kernel.org" ], "Received": [ "from hemlock.osuosl.org (smtp2.osuosl.org [140.211.166.133])\n\t(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))\n\t(No client certificate requested)\n\tby ozlabs.org (Postfix) with ESMTPS id 41FLqF2bWhz9ry1\n\tfor <incoming@patchwork.ozlabs.org>;\n\tTue, 26 Jun 2018 19:49:29 +1000 (AEST)", "from localhost (localhost [127.0.0.1])\n\tby hemlock.osuosl.org (Postfix) with ESMTP id F1B628745C;\n\tTue, 26 Jun 2018 09:49:27 +0000 (UTC)", "from hemlock.osuosl.org ([127.0.0.1])\n\tby localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)\n\twith ESMTP id xHqHWiVqws+R; Tue, 26 Jun 2018 09:49:24 +0000 (UTC)", "from ash.osuosl.org (ash.osuosl.org [140.211.166.34])\n\tby hemlock.osuosl.org (Postfix) with ESMTP id 8B07D86D78;\n\tTue, 26 Jun 2018 09:49:24 +0000 (UTC)", "from whitealder.osuosl.org (smtp1.osuosl.org [140.211.166.138])\n\tby ash.osuosl.org (Postfix) with ESMTP id E7D9C1BFC87\n\tfor <intel-wired-lan@lists.osuosl.org>;\n\tTue, 26 Jun 2018 09:49:23 +0000 (UTC)", "from localhost (localhost [127.0.0.1])\n\tby whitealder.osuosl.org (Postfix) with ESMTP id E2F5F814E7\n\tfor <intel-wired-lan@lists.osuosl.org>;\n\tTue, 26 Jun 2018 09:49:23 +0000 (UTC)", "from whitealder.osuosl.org ([127.0.0.1])\n\tby localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)\n\twith ESMTP id SS3D2oFOHs0u for <intel-wired-lan@lists.osuosl.org>;\n\tTue, 26 Jun 2018 09:49:22 +0000 (UTC)", "from osg.samsung.com (osg.samsung.com [64.30.133.232])\n\tby whitealder.osuosl.org (Postfix) with ESMTP id 84E3D8182B\n\tfor <intel-wired-lan@lists.osuosl.org>;\n\tTue, 26 Jun 2018 09:49:21 +0000 (UTC)", "from localhost (localhost [127.0.0.1])\n\tby osg.samsung.com (Postfix) with ESMTP id AEB9730BD0;\n\tTue, 26 Jun 2018 02:49:20 -0700 (PDT)", "from osg.samsung.com ([127.0.0.1])\n\tby localhost (localhost [127.0.0.1]) (amavisd-new, port 10024)\n\twith ESMTP id lbGDswAmJjxh; Tue, 26 Jun 2018 02:49:19 -0700 (PDT)", "from smtp.s-opensource.com (177.41.130.70.dynamic.adsl.gvt.net.br\n\t[177.41.130.70])\n\tby osg.samsung.com (Postfix) with ESMTPSA id 6E76630B88;\n\tTue, 26 Jun 2018 02:49:16 -0700 (PDT)", "from mchehab by smtp.s-opensource.com with local (Exim 4.91)\n\t(envelope-from <mchehab@smtp.s-opensource.com>)\n\tid 1fXkb4-0000mA-BG; Tue, 26 Jun 2018 06:49:14 -0300" ], "X-Virus-Scanned": [ "amavisd-new at osuosl.org", "amavisd-new at osuosl.org", "Debian amavisd-new at dev.s-opensource.com" ], "X-Amavis-Alert": [ "BAD HEADER SECTION, Duplicate header field: \"References\"", "BAD HEADER SECTION, Duplicate header field: \"References\"", "BAD HEADER SECTION, Duplicate header field: \"References\"" ], "X-Greylist": "from auto-whitelisted by SQLgrey-1.7.6", "From": "Mauro Carvalho Chehab <mchehab+samsung@kernel.org>", "To": "Linux Doc Mailing List <linux-doc@vger.kernel.org>", "Date": "Tue, 26 Jun 2018 06:49:10 -0300", "Message-Id": "<687412e4b938cdf17baf87b2961a48283edd7480.1530005114.git.mchehab+samsung@kernel.org>", "X-Mailer": "git-send-email 2.17.1", "In-Reply-To": [ "<cover.1530005114.git.mchehab+samsung@kernel.org>", "<cover.1530005114.git.mchehab+samsung@kernel.org>" ], "References": [ "<cover.1530005114.git.mchehab+samsung@kernel.org>", "<cover.1530005114.git.mchehab+samsung@kernel.org>" ], "Subject": "[Intel-wired-lan] [PATCH 8/9] networking: e1000.rst: Get rid of\n\tSphinx warnings", "X-BeenThere": "intel-wired-lan@osuosl.org", "X-Mailman-Version": "2.1.24", "Precedence": "list", "List-Id": "Intel Wired Ethernet Linux Kernel Driver Development\n\t<intel-wired-lan.osuosl.org>", "List-Unsubscribe": "<https://lists.osuosl.org/mailman/options/intel-wired-lan>, \n\t<mailto:intel-wired-lan-request@osuosl.org?subject=unsubscribe>", "List-Archive": "<http://lists.osuosl.org/pipermail/intel-wired-lan/>", "List-Post": "<mailto:intel-wired-lan@osuosl.org>", "List-Help": "<mailto:intel-wired-lan-request@osuosl.org?subject=help>", "List-Subscribe": "<https://lists.osuosl.org/mailman/listinfo/intel-wired-lan>, \n\t<mailto:intel-wired-lan-request@osuosl.org?subject=subscribe>", "Cc": "Jonathan Corbet <corbet@lwn.net>, netdev@vger.kernel.org,\n\tlinux-kernel@vger.kernel.org,\n\tMauro Carvalho Chehab <mchehab@infradead.org>, \n\tintel-wired-lan@lists.osuosl.org,\n\tMauro Carvalho Chehab <mchehab+samsung@kernel.org>,\n\t\"David S. Miller\" <davem@davemloft.net>", "MIME-Version": "1.0", "Content-Type": "text/plain; charset=\"us-ascii\"", "Content-Transfer-Encoding": "7bit", "Errors-To": "intel-wired-lan-bounces@osuosl.org", "Sender": "\"Intel-wired-lan\" <intel-wired-lan-bounces@osuosl.org>" }, "content": "Documentation/networking/e1000.rst:83: ERROR: Unexpected indentation.\n Documentation/networking/e1000.rst:84: WARNING: Block quote ends without a blank line; unexpected unindent.\n Documentation/networking/e1000.rst:173: WARNING: Definition list ends without a blank line; unexpected unindent.\n Documentation/networking/e1000.rst:236: WARNING: Definition list ends without a blank line; unexpected unindent.\n\nWhile here, fix highlights and mark a table as such.\n\nSigned-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>\n---\n Documentation/networking/e1000.rst | 187 +++++++++++++++++------------\n 1 file changed, 112 insertions(+), 75 deletions(-)", "diff": "diff --git a/Documentation/networking/e1000.rst b/Documentation/networking/e1000.rst\nindex 144b87eef153..f10dd4086921 100644\n--- a/Documentation/networking/e1000.rst\n+++ b/Documentation/networking/e1000.rst\n@@ -34,7 +34,8 @@ Command Line Parameters\n The default value for each parameter is generally the recommended setting,\n unless otherwise noted.\n \n-NOTES: For more information about the AutoNeg, Duplex, and Speed\n+NOTES:\n+\tFor more information about the AutoNeg, Duplex, and Speed\n parameters, see the \"Speed and Duplex Configuration\" section in\n this document.\n \n@@ -45,22 +46,27 @@ NOTES: For more information about the AutoNeg, Duplex, and Speed\n \n AutoNeg\n -------\n+\n (Supported only on adapters with copper connections)\n-Valid Range: 0x01-0x0F, 0x20-0x2F\n-Default Value: 0x2F\n+\n+:Valid Range: 0x01-0x0F, 0x20-0x2F\n+:Default Value: 0x2F\n \n This parameter is a bit-mask that specifies the speed and duplex settings\n advertised by the adapter. When this parameter is used, the Speed and\n Duplex parameters must not be specified.\n \n-NOTE: Refer to the Speed and Duplex section of this readme for more\n+NOTE:\n+ Refer to the Speed and Duplex section of this readme for more\n information on the AutoNeg parameter.\n \n Duplex\n ------\n+\n (Supported only on adapters with copper connections)\n-Valid Range: 0-2 (0=auto-negotiate, 1=half, 2=full)\n-Default Value: 0\n+\n+:Valid Range: 0-2 (0=auto-negotiate, 1=half, 2=full)\n+:Default Value: 0\n \n This defines the direction in which data is allowed to flow. Can be\n either one or two-directional. If both Duplex and the link partner are\n@@ -70,18 +76,22 @@ duplex.\n \n FlowControl\n -----------\n-Valid Range: 0-3 (0=none, 1=Rx only, 2=Tx only, 3=Rx&Tx)\n-Default Value: Reads flow control settings from the EEPROM\n+\n+:Valid Range: 0-3 (0=none, 1=Rx only, 2=Tx only, 3=Rx&Tx)\n+:Default Value: Reads flow control settings from the EEPROM\n \n This parameter controls the automatic generation(Tx) and response(Rx)\n to Ethernet PAUSE frames.\n \n InterruptThrottleRate\n ---------------------\n+\n (not supported on Intel(R) 82542, 82543 or 82544-based adapters)\n-Valid Range: 0,1,3,4,100-100000 (0=off, 1=dynamic, 3=dynamic conservative,\n- 4=simplified balancing)\n-Default Value: 3\n+\n+:Valid Range:\n+ 0,1,3,4,100-100000 (0=off, 1=dynamic, 3=dynamic conservative,\n+ 4=simplified balancing)\n+:Default Value: 3\n \n The driver can limit the amount of interrupts per second that the adapter\n will generate for incoming packets. It does this by writing a value to the\n@@ -135,13 +145,15 @@ Setting InterruptThrottleRate to 0 turns off any interrupt moderation\n and may improve small packet latency, but is generally not suitable\n for bulk throughput traffic.\n \n-NOTE: InterruptThrottleRate takes precedence over the TxAbsIntDelay and\n+NOTE:\n+ InterruptThrottleRate takes precedence over the TxAbsIntDelay and\n RxAbsIntDelay parameters. In other words, minimizing the receive\n and/or transmit absolute delays does not force the controller to\n generate more interrupts than what the Interrupt Throttle Rate\n allows.\n \n-CAUTION: If you are using the Intel(R) PRO/1000 CT Network Connection\n+CAUTION:\n+ If you are using the Intel(R) PRO/1000 CT Network Connection\n (controller 82547), setting InterruptThrottleRate to a value\n greater than 75,000, may hang (stop transmitting) adapters\n under certain network conditions. If this occurs a NETDEV\n@@ -151,7 +163,8 @@ CAUTION: If you are using the Intel(R) PRO/1000 CT Network Connection\n hang, ensure that InterruptThrottleRate is set no greater\n than 75,000 and is not set to 0.\n \n-NOTE: When e1000 is loaded with default settings and multiple adapters\n+NOTE:\n+ When e1000 is loaded with default settings and multiple adapters\n are in use simultaneously, the CPU utilization may increase non-\n linearly. In order to limit the CPU utilization without impacting\n the overall throughput, we recommend that you load the driver as\n@@ -168,9 +181,11 @@ NOTE: When e1000 is loaded with default settings and multiple adapters\n \n RxDescriptors\n -------------\n-Valid Range: 48-256 for 82542 and 82543-based adapters\n- 48-4096 for all other supported adapters\n-Default Value: 256\n+\n+:Valid Range:\n+ - 48-256 for 82542 and 82543-based adapters\n+ - 48-4096 for all other supported adapters\n+:Default Value: 256\n \n This value specifies the number of receive buffer descriptors allocated\n by the driver. Increasing this value allows the driver to buffer more\n@@ -180,15 +195,17 @@ Each descriptor is 16 bytes. A receive buffer is also allocated for each\n descriptor and can be either 2048, 4096, 8192, or 16384 bytes, depending\n on the MTU setting. The maximum MTU size is 16110.\n \n-NOTE: MTU designates the frame size. It only needs to be set for Jumbo\n+NOTE:\n+ MTU designates the frame size. It only needs to be set for Jumbo\n Frames. Depending on the available system resources, the request\n for a higher number of receive descriptors may be denied. In this\n case, use a lower number.\n \n RxIntDelay\n ----------\n-Valid Range: 0-65535 (0=off)\n-Default Value: 0\n+\n+:Valid Range: 0-65535 (0=off)\n+:Default Value: 0\n \n This value delays the generation of receive interrupts in units of 1.024\n microseconds. Receive interrupt reduction can improve CPU efficiency if\n@@ -198,7 +215,8 @@ of TCP traffic. If the system is reporting dropped receives, this value\n may be set too high, causing the driver to run out of available receive\n descriptors.\n \n-CAUTION: When setting RxIntDelay to a value other than 0, adapters may\n+CAUTION:\n+ When setting RxIntDelay to a value other than 0, adapters may\n hang (stop transmitting) under certain network conditions. If\n this occurs a NETDEV WATCHDOG message is logged in the system\n event log. In addition, the controller is automatically reset,\n@@ -207,9 +225,11 @@ CAUTION: When setting RxIntDelay to a value other than 0, adapters may\n \n RxAbsIntDelay\n -------------\n+\n (This parameter is supported only on 82540, 82545 and later adapters.)\n-Valid Range: 0-65535 (0=off)\n-Default Value: 128\n+\n+:Valid Range: 0-65535 (0=off)\n+:Default Value: 128\n \n This value, in units of 1.024 microseconds, limits the delay in which a\n receive interrupt is generated. Useful only if RxIntDelay is non-zero,\n@@ -220,9 +240,11 @@ conditions.\n \n Speed\n -----\n+\n (This parameter is supported only on adapters with copper connections.)\n-Valid Settings: 0, 10, 100, 1000\n-Default Value: 0 (auto-negotiate at all supported speeds)\n+\n+:Valid Settings: 0, 10, 100, 1000\n+:Default Value: 0 (auto-negotiate at all supported speeds)\n \n Speed forces the line speed to the specified value in megabits per second\n (Mbps). If this parameter is not specified or is set to 0 and the link\n@@ -231,22 +253,26 @@ speed. Duplex should also be set when Speed is set to either 10 or 100.\n \n TxDescriptors\n -------------\n-Valid Range: 48-256 for 82542 and 82543-based adapters\n- 48-4096 for all other supported adapters\n-Default Value: 256\n+\n+:Valid Range:\n+ - 48-256 for 82542 and 82543-based adapters\n+ - 48-4096 for all other supported adapters\n+:Default Value: 256\n \n This value is the number of transmit descriptors allocated by the driver.\n Increasing this value allows the driver to queue more transmits. Each\n descriptor is 16 bytes.\n \n-NOTE: Depending on the available system resources, the request for a\n+NOTE:\n+ Depending on the available system resources, the request for a\n higher number of transmit descriptors may be denied. In this case,\n use a lower number.\n \n TxIntDelay\n ----------\n-Valid Range: 0-65535 (0=off)\n-Default Value: 8\n+\n+:Valid Range: 0-65535 (0=off)\n+:Default Value: 8\n \n This value delays the generation of transmit interrupts in units of\n 1.024 microseconds. Transmit interrupt reduction can improve CPU\n@@ -256,9 +282,11 @@ causing the driver to run out of available transmit descriptors.\n \n TxAbsIntDelay\n -------------\n+\n (This parameter is supported only on 82540, 82545 and later adapters.)\n-Valid Range: 0-65535 (0=off)\n-Default Value: 32\n+\n+:Valid Range: 0-65535 (0=off)\n+:Default Value: 32\n \n This value, in units of 1.024 microseconds, limits the delay in which a\n transmit interrupt is generated. Useful only if TxIntDelay is non-zero,\n@@ -269,18 +297,21 @@ network conditions.\n \n XsumRX\n ------\n+\n (This parameter is NOT supported on the 82542-based adapter.)\n-Valid Range: 0-1\n-Default Value: 1\n+\n+:Valid Range: 0-1\n+:Default Value: 1\n \n A value of '1' indicates that the driver should enable IP checksum\n offload for received packets (both UDP and TCP) to the adapter hardware.\n \n Copybreak\n ---------\n-Valid Range: 0-xxxxxxx (0=off)\n-Default Value: 256\n-Usage: modprobe e1000.ko copybreak=128\n+\n+:Valid Range: 0-xxxxxxx (0=off)\n+:Default Value: 256\n+:Usage: modprobe e1000.ko copybreak=128\n \n Driver copies all packets below or equaling this size to a fresh RX\n buffer before handing it up the stack.\n@@ -292,8 +323,9 @@ it is also available during runtime at\n \n SmartPowerDownEnable\n --------------------\n-Valid Range: 0-1\n-Default Value: 0 (disabled)\n+\n+:Valid Range: 0-1\n+:Default Value: 0 (disabled)\n \n Allows PHY to turn off in lower power states. The user can turn off\n this parameter in supported chipsets.\n@@ -309,14 +341,14 @@ fiber interface board only links at 1000 Mbps full-duplex.\n \n For copper-based boards, the keywords interact as follows:\n \n- The default operation is auto-negotiate. The board advertises all\n+- The default operation is auto-negotiate. The board advertises all\n supported speed and duplex combinations, and it links at the highest\n common speed and duplex mode IF the link partner is set to auto-negotiate.\n \n- If Speed = 1000, limited auto-negotiation is enabled and only 1000 Mbps\n+- If Speed = 1000, limited auto-negotiation is enabled and only 1000 Mbps\n is advertised (The 1000BaseT spec requires auto-negotiation.)\n \n- If Speed = 10 or 100, then both Speed and Duplex should be set. Auto-\n+- If Speed = 10 or 100, then both Speed and Duplex should be set. Auto-\n negotiation is disabled, and the AutoNeg parameter is ignored. Partner\n SHOULD also be forced.\n \n@@ -328,13 +360,15 @@ process.\n The parameter may be specified as either a decimal or hexadecimal value as\n determined by the bitmap below.\n \n+============== ====== ====== ======= ======= ====== ====== ======= ======\n Bit position 7 6 5 4 3 2 1 0\n Decimal Value 128 64 32 16 8 4 2 1\n Hex value 80 40 20 10 8 4 2 1\n Speed (Mbps) N/A N/A 1000 N/A 100 100 10 10\n Duplex Full Full Half Full Half\n+============== ====== ====== ======= ======= ====== ====== ======= ======\n \n-Some examples of using AutoNeg:\n+Some examples of using AutoNeg::\n \n modprobe e1000 AutoNeg=0x01 (Restricts autonegotiation to 10 Half)\n modprobe e1000 AutoNeg=1 (Same as above)\n@@ -357,56 +391,59 @@ Additional Configurations\n \n Jumbo Frames\n ------------\n-Jumbo Frames support is enabled by changing the MTU to a value larger\n-than the default of 1500. Use the ifconfig command to increase the MTU\n-size. For example::\n+\n+ Jumbo Frames support is enabled by changing the MTU to a value larger than\n+ the default of 1500. Use the ifconfig command to increase the MTU size.\n+ For example::\n \n ifconfig eth<x> mtu 9000 up\n \n-This setting is not saved across reboots. It can be made permanent if\n-you add::\n+ This setting is not saved across reboots. It can be made permanent if\n+ you add::\n \n MTU=9000\n \n-to the file /etc/sysconfig/network-scripts/ifcfg-eth<x>. This example\n-applies to the Red Hat distributions; other distributions may store this\n-setting in a different location.\n+ to the file /etc/sysconfig/network-scripts/ifcfg-eth<x>. This example\n+ applies to the Red Hat distributions; other distributions may store this\n+ setting in a different location.\n \n-Notes: Degradation in throughput performance may be observed in some\n-Jumbo frames environments. If this is observed, increasing the\n-application's socket buffer size and/or increasing the\n-/proc/sys/net/ipv4/tcp_*mem entry values may help. See the specific\n-application manual and /usr/src/linux*/Documentation/\n-networking/ip-sysctl.txt for more details.\n+Notes:\n+ Degradation in throughput performance may be observed in some Jumbo frames\n+ environments. If this is observed, increasing the application's socket buffer\n+ size and/or increasing the /proc/sys/net/ipv4/tcp_*mem entry values may help.\n+ See the specific application manual and /usr/src/linux*/Documentation/\n+ networking/ip-sysctl.txt for more details.\n \n-- The maximum MTU setting for Jumbo Frames is 16110. This value\n- coincides with the maximum Jumbo Frames size of 16128.\n+ - The maximum MTU setting for Jumbo Frames is 16110. This value coincides\n+ with the maximum Jumbo Frames size of 16128.\n \n-- Using Jumbo frames at 10 or 100 Mbps is not supported and may result\n- in poor performance or loss of link.\n+ - Using Jumbo frames at 10 or 100 Mbps is not supported and may result in\n+ poor performance or loss of link.\n \n-- Adapters based on the Intel(R) 82542 and 82573V/E controller do not\n- support Jumbo Frames. These correspond to the following product names:\n- Intel(R) PRO/1000 Gigabit Server Adapter Intel(R) PRO/1000 PM Network\n- Connection\n+ - Adapters based on the Intel(R) 82542 and 82573V/E controller do not\n+ support Jumbo Frames. These correspond to the following product names::\n+\n+ Intel(R) PRO/1000 Gigabit Server Adapter\n+ Intel(R) PRO/1000 PM Network Connection\n \n ethtool\n -------\n-The driver utilizes the ethtool interface for driver configuration and\n-diagnostics, as well as displaying statistical information. The ethtool\n-version 1.6 or later is required for this functionality.\n \n-The latest release of ethtool can be found from\n-https://www.kernel.org/pub/software/network/ethtool/\n+ The driver utilizes the ethtool interface for driver configuration and\n+ diagnostics, as well as displaying statistical information. The ethtool\n+ version 1.6 or later is required for this functionality.\n+\n+ The latest release of ethtool can be found from\n+ https://www.kernel.org/pub/software/network/ethtool/\n \n Enabling Wake on LAN* (WoL)\n ---------------------------\n-WoL is configured through the ethtool* utility.\n \n-WoL will be enabled on the system during the next shut down or reboot.\n-For this driver version, in order to enable WoL, the e1000 driver must be\n-loaded when shutting down or rebooting the system.\n+ WoL is configured through the ethtool* utility.\n \n+ WoL will be enabled on the system during the next shut down or reboot.\n+ For this driver version, in order to enable WoL, the e1000 driver must be\n+ loaded when shutting down or rebooting the system.\n \n Support\n =======\n", "prefixes": [ "8/9" ] }