public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <error27@gmail.com>
To: horms@vergenet.net
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Peter Huewe <PeterHuewe@gmx.de>
Subject: [patch] otus: zfTkipInit(): increment another pointer
Date: Sat, 9 Jan 2010 11:44:05 +0300	[thread overview]
Message-ID: <20100109084405.GC7840@bicker> (raw)
In-Reply-To: <20100108075921.305507492@vergenet.net>

This applies on top of Simon Horman's patch set, particularly [patch 5/6].  
Feel free to roll them into one and change the sign-off to yourself.

There was another pointer that needed to be incremented.  Now all six
of the bytes are used.

Signed-off-by: Dan Carpenter <error27@gmail.com>

--- orig/drivers/staging/otus/80211core/ctkip.c	2010-01-09 00:46:14.000000000 +0300
+++ devel/drivers/staging/otus/80211core/ctkip.c	2010-01-09 00:48:39.000000000 +0300
@@ -255,7 +255,8 @@ void zfTkipInit(u8_t* key, u8_t* ta, str
     zfMemoryCopy(pSeed->ta, ta, 6);
     zfMemoryCopy(pSeed->tk, key, 16);
 
-    iv16 = *initIv++;
+    iv16 = *initIv;
+    initIv++;
     iv16 += *initIv<<8;
     initIv++;
 

  reply	other threads:[~2010-01-09  8:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-08  7:57 [patch 0/6] otus: build fixes horms
2010-01-08  7:57 ` [patch 1/6] otus: dont mix declarations and code horms
2010-01-08  7:57 ` [patch 2/6] otus: remove unused variables horms
2010-01-08  7:57 ` [patch 3/6] otus: remove unused constants horms
2010-01-08  7:57 ` [patch 4/6] otus: Fix ZM_SEQ_DEBUG macro for no-debug case horms
2010-01-08  7:57 ` [patch 5/6] otus: zfTkipInit(): increment pointer horms
2010-01-09  8:44   ` Dan Carpenter [this message]
2010-01-12  0:50     ` [patch] tch 5/6 v2] otus: zfTkipInit(): increment another pointer Simon Horman
2010-01-08  7:57 ` [patch 6/6] otus: zfRateCtrlRateDiff(): remove duplicate comparison horms
2010-01-09  8:44   ` Dan Carpenter
2010-01-11 13:06     ` Simon Horman

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=20100109084405.GC7840@bicker \
    --to=error27@gmail.com \
    --cc=PeterHuewe@gmx.de \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=horms@vergenet.net \
    --cc=linux-kernel@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