mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nick Andrew <nick@nick-andrew.net>
To: Ishizaki Kou <kou.ishizaki@toshiba.co.jp>,
	Jeff Garzik <jgarzik@pobox.com>, Jeff Garzik <jgarzik@redhat.com>,
	Jens Osterkamp <jens@de.ibm.com>,
	Kou Ishizaki <kou.ishizaki@toshiba.co.jp>,
	Nick Andrew <nick@nick-andrew.net>,
	Qinghuang Feng <qhfeng.kernel@gmail.com>,
	netdev@vger.kernel.org
Cc: <linux-kernel@vger.kernel.org>, Nick Andrew <nick@nick-andrew.net>
Subject: [PATCH] Fix incorrect use of loose in spider_net.c
Date: Fri, 05 Dec 2008 14:08:03 +1100	[thread overview]
Message-ID: <20081205030803.32099.345.stgit@marcab.local.tull.net> (raw)

Fix incorrect use of loose in spider_net.c

It should be 'lose', not 'loose'.

Signed-off-by: Nick Andrew <nick@nick-andrew.net>
---

 drivers/net/spider_net.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)


diff --git a/drivers/net/spider_net.c b/drivers/net/spider_net.c
index 07599b4..325fbc9 100644
--- a/drivers/net/spider_net.c
+++ b/drivers/net/spider_net.c
@@ -789,7 +789,7 @@ spider_net_set_low_watermark(struct spider_net_card *card)
  * spider_net_release_tx_chain releases the tx descriptors that spider has
  * finished with (if non-brutal) or simply release tx descriptors (if brutal).
  * If some other context is calling this function, we return 1 so that we're
- * scheduled again (if we were scheduled) and will not loose initiative.
+ * scheduled again (if we were scheduled) and will not lose initiative.
  */
 static int
 spider_net_release_tx_chain(struct spider_net_card *card, int brutal)



             reply	other threads:[~2008-12-05 10:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-05  3:08 Nick Andrew [this message]
2008-12-07  7:57 ` 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=20081205030803.32099.345.stgit@marcab.local.tull.net \
    --to=nick@nick-andrew.net \
    --cc=jens@de.ibm.com \
    --cc=jgarzik@pobox.com \
    --cc=jgarzik@redhat.com \
    --cc=kou.ishizaki@toshiba.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=qhfeng.kernel@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome