From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Jouni Malinen <jouni@qca.qualcomm.com>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 2/3] ath6kl: Fix key configuration to copy at most seq_len from seq
Date: Thu, 3 Nov 2011 19:05:30 +0200 [thread overview]
Message-ID: <4EB2C9DA.10905@qca.qualcomm.com> (raw)
In-Reply-To: <20111102214555.GA31245@jouni.qca.qualcomm.com>
On 11/02/2011 11:45 PM, Jouni Malinen wrote:
> There is no guarantee on the caller using 8-octet buffer for
> key->seq, so better follow the key->seq_len parameter on figuring
> out how many octets to copy.
Thanks, I applied this patch. As discussed privately, "2/3" was just a
leftover and I ignored it.
Kalle
prev parent reply other threads:[~2011-11-03 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 21:45 [PATCH 2/3] ath6kl: Fix key configuration to copy at most seq_len from seq Jouni Malinen
2011-11-03 17:05 ` Kalle Valo [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=4EB2C9DA.10905@qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=jouni@qca.qualcomm.com \
--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).