Skip to content

Commit

Permalink
fix comment typos concerning "challenge"
Browse files Browse the repository at this point in the history
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
  • Loading branch information
Uwe Kleine-König authored and Jiri Kosina committed Jul 19, 2010
1 parent 9d910c9 commit 25d1fbf
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion drivers/net/wireless/hostap/hostap_ap.c
Original file line number Diff line number Diff line change
Expand Up @@ -1225,7 +1225,7 @@ static void ap_crypt_init(struct ap_data *ap)


/* Generate challenge data for shared key authentication. IEEE 802.11 specifies
* that WEP algorithm is used for generating challange. This should be unique,
* that WEP algorithm is used for generating challenge. This should be unique,
* but otherwise there is not really need for randomness etc. Initialize WEP
* with pseudo random key and then use increasing IV to get unique challenge
* streams.
Expand Down
2 changes: 1 addition & 1 deletion sound/soc/imx/imx-ssi.c
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@
* between pcm data and GPIO status data changes. Our FIQ handler is not
* able to handle this, hence this driver only works with 48000Hz sampling
* rate.
* Reading and writing AC97 registers is another challange. The core
* Reading and writing AC97 registers is another challenge. The core
* provides us status bits when the read register is updated with *another*
* value. When we read the same register two times (and the register still
* contains the same value) these status bits are not set. We work
Expand Down

0 comments on commit 25d1fbf

Please sign in to comment.