Return-path: Received: from mail-pb0-f46.google.com ([209.85.160.46]:45828 "EHLO mail-pb0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757461Ab2IKQai (ORCPT ); Tue, 11 Sep 2012 12:30:38 -0400 Received: by pbbrr13 with SMTP id rr13so1023188pbb.19 for ; Tue, 11 Sep 2012 09:30:38 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <1346146446-628-1-git-send-email-yeohchunyeow@gmail.com> <1346746298.3737.0.camel@jlt4.sipsolutions.net> <20120904102204.GA2541@w1.fi> <1346758521.3737.28.camel@jlt4.sipsolutions.net> <20120905071653.GB3629@w1.fi> <20120905080336.GA4747@w1.fi> <87zk4y3tsz.fsf@purkki.adurom.net> Date: Tue, 11 Sep 2012 09:30:38 -0700 Message-ID: (sfid-20120911_183043_837154_AC86F8B1) Subject: Re: [PATCH] ath5k: add support of HW encryption in management frames From: Adrian Chadd To: Yeoh Chun-Yeow Cc: Nick Kossifidis , Kalle Valo , Jouni Malinen , Johannes Berg , linux-wireless@vger.kernel.org, jirislaby@gmail.com, mcgrof@qca.qualcomm.com, ath5k-devel@venema.h4ckr.net Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: This is why I asked for a bit of a summary. What specific behaviour are you chasing from the keycache, source/destination MAC address matching and encryption engine? There've apparently been some keycache matching bugs in the past .. Adrian