linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Andriy Tkachuk <andriy.tkachuk@gmail.com>
Cc: linux-wireless@vger.kernel.org, Jouni Malinen <j@w1.fi>
Subject: Re: [PATCH] lib80211: Introduce TKIP_HDR_LEN define for code clarity
Date: Tue, 2 Feb 2010 09:31:41 -0500	[thread overview]
Message-ID: <20100202143140.GA15782@tuxdriver.com> (raw)
In-Reply-To: <4B68084E.7080306@gmail.com>

On Tue, Feb 02, 2010 at 01:11:10PM +0200, Andriy Tkachuk wrote:
> Introduce TKIP_HDR_LEN define for code clarity (in the same way as
> CCMP_HDR_LEN).
> 
> Also odd len variable (not used) dropped from lib80211_tkip_hdr().
> 
> Signed-off-by: Andriy V. Tkachuk <andrit@ukr.net>
> 
> ---
>  net/wireless/lib80211_crypt_tkip.c |   12 ++++++------
>  1 files changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/net/wireless/lib80211_crypt_tkip.c
> b/net/wireless/lib80211_crypt_tkip.c
> index c362873..c4fb4fb 100644
> --- a/net/wireless/lib80211_crypt_tkip.c
> +++ b/net/wireless/lib80211_crypt_tkip.c
> @@ -36,6 +36,8 @@ MODULE_AUTHOR("Jouni Malinen");
>  MODULE_DESCRIPTION("lib80211 crypt: TKIP");
>  MODULE_LICENSE("GPL");
> 
> +#define TKIP_HDR_LEN 8
> +
>  struct lib80211_tkip_data {
>  #define TKIP_KEY_LEN 32
>  	u8 key[TKIP_KEY_LEN];
> @@ -314,13 +316,12 @@ static int lib80211_tkip_hdr(struct sk_buff *skb,
> int hdr_len,

After a quick look, this and the other patch look fine.  But, the
patches are whitespace-damaged.  I can fix these, but in the future
please be sure to use a mailer that does not break lines.  I recommend
mutt and/or 'git send-email'.

Thanks,

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2010-02-02 15:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-02 11:11 [PATCH] lib80211: Introduce TKIP_HDR_LEN define for code clarity Andriy Tkachuk
2010-02-02 14:31 ` John W. Linville [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-02-02 14:33 Andriy Tkachuk

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=20100202143140.GA15782@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=andriy.tkachuk@gmail.com \
    --cc=j@w1.fi \
    --cc=linux-wireless@vger.kernel.org \
    /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).