[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKv+Gu-qbwCJzH2TMpe5hEh8UAO3XQ66Zzf9Nx4UqBXd3Lr79w@mail.gmail.com>
Date: Fri, 16 Aug 2019 11:31:23 +0300
From: Ard Biesheuvel <ard.biesheuvel@...aro.org>
To: Christina Quast <contact@...istina-quast.de>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Payal Kshirsagar <payal.s.kshirsagar.98@...il.com>,
Eric Biggers <ebiggers@...gle.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
"open list:ANDROID DRIVERS" <devel@...verdev.osuosl.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Anushka Shukla <anushkacharu9@...il.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
Zach Turner <turnerzdp@...il.com>,
"<linux-wireless@...r.kernel.org>" <linux-wireless@...r.kernel.org>,
Johannes Berg <johannes@...solutions.net>,
"David S. Miller" <davem@...emloft.net>,
"open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
<linux-crypto@...r.kernel.org>
Subject: Re: [PATCH 0/2] Use ccm(aes) aead transform in staging drivers
On Fri, 16 Aug 2019 at 10:00, Christina Quast
<contact@...istina-quast.de> wrote:
>
> Use ccm(aes) aead transform instead of invoking the AES block cipher
> block by block.
>
Thanks! This eliminates another two users of the bare cipher API,
which is not the right abstraction for drivers to use.
Reviewed-by: Ard Biesheuvel <ard.biesheuvel@...aro.org>
I don't have the hardware, so I can't test this.
> Christina Quast (2):
> staging: rtl8192u: ieee80211: ieee80211_crypt_ccmp.c: Use crypto API
> ccm(aes)
> staging: rtl8192e: rtllib_crypt_ccmp.c: Use crypto API ccm(aes)
>
> drivers/staging/rtl8192e/Kconfig | 1 +
> drivers/staging/rtl8192e/rtllib_crypt_ccmp.c | 187 ++++++++----------
> drivers/staging/rtl8192u/Kconfig | 2 +
> .../rtl8192u/ieee80211/ieee80211_crypt_ccmp.c | 187 ++++++++----------
> 4 files changed, 159 insertions(+), 218 deletions(-)
>
> --
> 2.20.1
>
Powered by blists - more mailing lists