Re: [PATCH] Fix typo interrest[ing|ed] => interest[ing|ed]

[Jiri Kosina]

On Mon, 20 Sep 2010, Thomas Weber wrote:

> Fix typos with interrest*.
> 
> Signed-off-by: Thomas Weber <weber@xxxxxxxxxxxxx>
> ---
>  drivers/char/stallion.c |    4 ++--
>  drivers/net/wan/hdlc.c  |    2 +-
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/char/stallion.c b/drivers/char/stallion.c
> index f2167f8..d7d7d4f 100644
> --- a/drivers/char/stallion.c
> +++ b/drivers/char/stallion.c
> @@ -3180,7 +3180,7 @@ static void stl_cd1400flush(struct stlport *portp)
>  
>  /*
>   *	Return the current state of data flow on this port. This is only
> - *	really interresting when determining if data has fully completed
> + *	really interesting when determining if data has fully completed
>   *	transmission or not... This is easy for the cd1400, it accurately
>   *	maintains the busy port flag.
>   */
> @@ -4130,7 +4130,7 @@ static void stl_sc26198flush(struct stlport *portp)
>  
>  /*
>   *	Return the current state of data flow on this port. This is only
> - *	really interresting when determining if data has fully completed
> + *	really interesting when determining if data has fully completed
>   *	transmission or not... The sc26198 interrupt scheme cannot
>   *	determine when all data has actually drained, so we need to
>   *	check the port statusy register to be sure.
> diff --git a/drivers/net/wan/hdlc.c b/drivers/net/wan/hdlc.c
> index 9937bba..5d4bb61 100644
> --- a/drivers/net/wan/hdlc.c
> +++ b/drivers/net/wan/hdlc.c
> @@ -109,7 +109,7 @@ static int hdlc_device_event(struct notifier_block *this, unsigned long event,
>  		return NOTIFY_DONE; /* not an HDLC device */
>  
>  	if (event != NETDEV_CHANGE)
> -		return NOTIFY_DONE; /* Only interrested in carrier changes */
> +		return NOTIFY_DONE; /* Only interested in carrier changes */
>  
>  	on = netif_carrier_ok(dev);
>  

Applied, thanks.

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