From: Johannes Berg <johannes@sipsolutions.net>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org,
Tomas Winkler <tomas.winkler@intel.com>
Subject: Re: [PATCH 1/1] IWL: fix WARN typo
Date: Mon, 05 Jan 2009 20:02:18 +0100 [thread overview]
Message-ID: <1231182138.3697.0.camel@johannes> (raw)
In-Reply-To: <1231171404-22822-1-git-send-email-jirislaby@gmail.com> (sfid-20090105_170346_728743_CFC4B367)
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
On Mon, 2009-01-05 at 17:03 +0100, Jiri Slaby wrote:
> new kew -> a new key
>
> Signed-off-by: Jiri Slaby <jirislaby@gmail.com>
> Cc: Tomas Winkler <tomas.winkler@intel.com>
> Cc: John W. Linville <linville@tuxdriver.com>
> ---
> drivers/net/wireless/iwlwifi/iwl-sta.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/net/wireless/iwlwifi/iwl-sta.c b/drivers/net/wireless/iwlwifi/iwl-sta.c
> index 412f66b..b28564a 100644
> --- a/drivers/net/wireless/iwlwifi/iwl-sta.c
> +++ b/drivers/net/wireless/iwlwifi/iwl-sta.c
> @@ -638,7 +638,7 @@ static int iwl_set_wep_dynamic_key_info(struct iwl_priv *priv,
> * in uCode. */
>
> WARN(priv->stations[sta_id].sta.key.key_offset == WEP_INVALID_OFFSET,
> - "no space for new kew");
> + "no space for a new key");
Eh, if anything shouldn't that be "the new key"?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2009-01-05 19:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 16:03 [PATCH 1/1] IWL: fix WARN typo Jiri Slaby
2009-01-05 16:04 ` Jiri Slaby
2009-01-05 16:06 ` [PATCH 1/1 #2] " Jiri Slaby
2009-01-09 20:18 ` John W. Linville
2009-01-09 21:42 ` John W. Linville
2009-01-09 22:20 ` Johannes Berg
2009-01-05 19:02 ` Johannes Berg [this message]
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=1231182138.3697.0.camel@johannes \
--to=johannes@sipsolutions.net \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=tomas.winkler@intel.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;
as well as URLs for NNTP newsgroup(s).