All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: davem@davemloft.net
Cc: Jean Sacren <sakiwit@gmail.com>,
	netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com,
	jogreene@redhat.com, Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Subject: [net-next 08/17] e1000: fix a typo in the comment
Date: Sun, 13 Dec 2015 00:31:21 -0800	[thread overview]
Message-ID: <1449995490-17020-9-git-send-email-jeffrey.t.kirsher@intel.com> (raw)
In-Reply-To: <1449995490-17020-1-git-send-email-jeffrey.t.kirsher@intel.com>

From: Jean Sacren <sakiwit@gmail.com>

Use 'That' to replace 'The' so that the comment would make sense.

Signed-off-by: Jean Sacren <sakiwit@gmail.com>
Tested-by: Aaron Brown <aaron.f.brown@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
---
 drivers/net/ethernet/intel/e1000/e1000_main.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/ethernet/intel/e1000/e1000_main.c b/drivers/net/ethernet/intel/e1000/e1000_main.c
index a0f3a31..3fc7bde 100644
--- a/drivers/net/ethernet/intel/e1000/e1000_main.c
+++ b/drivers/net/ethernet/intel/e1000/e1000_main.c
@@ -1263,7 +1263,7 @@ err_pci_reg:
  * @pdev: PCI device information struct
  *
  * e1000_remove is called by the PCI subsystem to alert the driver
- * that it should release a PCI device.  The could be caused by a
+ * that it should release a PCI device. That could be caused by a
  * Hot-Plug event, or because the driver is going to be removed from
  * memory.
  **/
-- 
2.5.0

  parent reply	other threads:[~2015-12-13  8:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-13  8:31 [net-next 00/17][pull request] 1GbE Intel Wired LAN Driver Updates 2015-12-12 Jeff Kirsher
2015-12-13  8:31 ` [net-next 01/17] e1000: make eeprom read/write scheduler friendly Jeff Kirsher
2015-12-13  8:31 ` [net-next 02/17] igb: add 88E1543 initialization code Jeff Kirsher
2015-12-13  8:31 ` [net-next 03/17] e1000: fix data race between tx_ring->next_to_clean Jeff Kirsher
2015-12-13  8:31 ` [net-next 04/17] igb: don't unmap NULL hw_addr Jeff Kirsher
2015-12-13  8:31 ` [net-next 05/17] e1000: Remove checkpatch coding style errors Jeff Kirsher
2015-12-13  8:31 ` [net-next 06/17] igb: use the correct i210 register for EEMNGCTL Jeff Kirsher
2015-12-13  8:31 ` [net-next 07/17] e1000: clean up the checking logic Jeff Kirsher
2015-12-13  8:31 ` Jeff Kirsher [this message]
2015-12-13  8:31 ` [net-next 09/17] e1000e: clean up the local variable Jeff Kirsher
2015-12-13  8:31 ` [net-next 10/17] e1000: fix kernel-doc argument being missing Jeff Kirsher
2015-12-13  8:31 ` [net-next 11/17] e1000: get rid of duplicate exit path Jeff Kirsher
2015-12-13  8:31 ` [net-next 12/17] e1000: Elementary checkpatch warnings and checks removed Jeff Kirsher
2015-12-13  8:31 ` [net-next 13/17] e1000e: fix division by zero on jumbo MTUs Jeff Kirsher
2015-12-13  8:31 ` [net-next 14/17] e1000e: Increase timeout of polling bit RSPCIPHY Jeff Kirsher
2015-12-13  8:31 ` [net-next 15/17] igb: fix NULL derefs due to skipped SR-IOV enabling Jeff Kirsher
2015-12-13  8:31 ` [net-next 16/17] igb: improve handling of disconnected adapters Jeff Kirsher
2015-12-13  8:31 ` [net-next 17/17] e1000e: initial support for i219-LM (3) Jeff Kirsher
2015-12-13 22:11 ` [net-next 00/17][pull request] 1GbE Intel Wired LAN Driver Updates 2015-12-12 David Miller

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=1449995490-17020-9-git-send-email-jeffrey.t.kirsher@intel.com \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=davem@davemloft.net \
    --cc=jogreene@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@redhat.com \
    --cc=sakiwit@gmail.com \
    --cc=sassmann@redhat.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.