linux-kernel - [PATCH] Fix incorrect use of loose in i2o

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081205030801.32014.92677.stgit@marcab.local.tull.net>
Date:	Fri, 05 Dec 2008 14:08:01 +1100
From:	Nick Andrew <nick@...k-andrew.net>
To:	"Jun'ichi Nomura" <j-nomura@...jp.nec.com>,
	Al Viro <viro@...iv.linux.org.uk>,
	Kiyoshi Ueda <k-ueda@...jp.nec.com>,
	Nick Andrew <nick@...k-andrew.net>,
	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	<linux-kernel@...r.kernel.org>, Nick Andrew <nick@...k-andrew.net>
Subject: [PATCH] Fix incorrect use of loose in i2o_block.c

Fix incorrect use of loose in i2o_block.c

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

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

 drivers/message/i2o/i2o_block.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)


diff --git a/drivers/message/i2o/i2o_block.c b/drivers/message/i2o/i2o_block.c
index 84bdc2e..a443e13 100644
--- a/drivers/message/i2o/i2o_block.c
+++ b/drivers/message/i2o/i2o_block.c
@@ -354,7 +354,7 @@ static inline void i2o_block_sglist_free(struct i2o_block_request *ireq)
  *	@req: the request to prepare
  *
  *	Allocate the necessary i2o_block_request struct and connect it to
- *	the request. This is needed that we not loose the SG list later on.
+ *	the request. This is needed that we not lose the SG list later on.
  *
  *	Returns BLKPREP_OK on success or BLKPREP_DEFER on failure.
  */


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/