linux-kernel - Re: [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-prev] [day] [month] [year] [list]

Message-Id: <20081217163429.225c5706.randy.dunlap@oracle.com>
Date:	Wed, 17 Dec 2008 16:34:29 -0800
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Nick Andrew <nick@...k-andrew.net>
Cc:	"Jun'ichi Nomura" <j-nomura@...jp.nec.com>,
	Al Viro <viro@...iv.linux.org.uk>,
	Kiyoshi Ueda <k-ueda@...jp.nec.com>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Fix incorrect use of loose in i2o_block.c

On Fri, 05 Dec 2008 14:08:01 +1100 Nick Andrew wrote:

> Fix incorrect use of loose in i2o_block.c
> 
> It should be 'lose', not 'loose'.
> 
> Signed-off-by: Nick Andrew <nick@...k-andrew.net>

Acked-by: Randy Dunlap <randy.dunlap@...cle.com> # sorry about the delayed reply


> ---
> 
>  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.
>   */


---
~Randy
--
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/