From: Johannes Berg <johannes@sipsolutions.net>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: backports@vger.kernel.org
Subject: Re: [PATCH 07/21] backports: add backport for new AEAD crypto API
Date: Tue, 16 Jun 2015 10:56:28 +0200 [thread overview]
Message-ID: <1434444988.2337.11.camel@sipsolutions.net> (raw)
In-Reply-To: <1434292162-2261-8-git-send-email-hauke@hauke-m.de> (sfid-20150614_162945_019275_3F6B4430)
On Sun, 2015-06-14 at 16:29 +0200, Hauke Mehrtens wrote:
> mac80211 makes use of the new AEAD crypto api since commit 957e0fe629.
> This patch provides a backport layer which converts the new API to the
> old one used in older kernel versions. This backport is based on this
> mainline commit: 996d98d85.
This looks right to me.
johannes
next prev parent reply other threads:[~2015-06-16 8:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-14 14:29 [PATCH 00/21] backports: bring it to next-20150612 and add mt7601u Hauke Mehrtens
2015-06-14 14:29 ` [PATCH 01/21] patches: fix spatch for bluetooth Hauke Mehrtens
2015-06-14 14:29 ` [PATCH 02/21] patches: deactivate tracing for ath6kl, cfg80211 and wil6210 only on kernel < 3.4 Hauke Mehrtens
2015-06-15 7:02 ` Johannes Berg
2015-06-15 18:20 ` Hauke Mehrtens
2015-06-14 14:29 ` [PATCH 03/21] patches: include linux/sched.h header in drivers/nfc/mei_phy.c Hauke Mehrtens
2015-06-14 14:29 ` [PATCH 04/21] header: fix rt6_nexthop() backport Hauke Mehrtens
2015-06-14 14:29 ` [PATCH 05/21] patches: remove additional member in struct mei_cl_device_id Hauke Mehrtens
2015-06-14 14:29 ` [PATCH 06/21] patches: rhashtable header patch not needed Hauke Mehrtens
2015-06-14 14:29 ` [PATCH 07/21] backports: add backport for new AEAD crypto API Hauke Mehrtens
2015-06-16 8:56 ` Johannes Berg [this message]
2015-06-14 14:29 ` [PATCH 08/21] dependencies: add VIDEO_COBALT Hauke Mehrtens
2015-06-14 14:29 ` [PATCH 09/21] dependencies: make DVB_M88DS3103 and DVB_TS2020 depend on kernel > 3.8 Hauke Mehrtens
2015-06-14 14:29 ` [PATCH 10/21] dependencies: make two media tuners depend on kernel >= 3.3 Hauke Mehrtens
2015-06-14 14:29 ` [PATCH 11/21] dependencies: make VIDEO_ADV7604 depend on kernel >= 3.17 Hauke Mehrtens
2015-06-14 14:29 ` [PATCH 12/21] dependencies: make VIDEO_ADP1653 depend on kernel >= 3.13 Hauke Mehrtens
2015-06-14 14:29 ` [PATCH 13/21] backports: add HDMI driver Hauke Mehrtens
2015-06-14 14:29 ` [PATCH 14/21] patches: do not use vidioc_expbuf function pointer in v4l Hauke Mehrtens
2015-06-14 14:29 ` [PATCH 15/21] backports: add tty_set_termios() Hauke Mehrtens
2015-06-14 14:29 ` [PATCH 16/21] header: add dev_dbg_once() and others Hauke Mehrtens
2015-06-14 14:29 ` [PATCH 17/21] header: add devm_kcalloc() Hauke Mehrtens
2015-06-14 14:29 ` [PATCH 18/21] backports: add mediatek mt7601u driver Hauke Mehrtens
2015-06-14 14:29 ` [PATCH 19/21] patches: deactivate struct tracing in mt7601u Hauke Mehrtens
2015-06-14 14:29 ` [PATCH 20/21] patches: deactivate tracing on mt7601u for kernel < 3.4 Hauke Mehrtens
2015-06-14 14:29 ` [PATCH 21/21] patches: refresh patches on next-20150612 Hauke Mehrtens
2015-06-15 21:13 ` [PATCH v2 02/22] patches: fix tracing on older kernels for cfg80211, ath6kl and wil6210 Hauke Mehrtens
2015-06-15 21:14 ` [PATCH v2 22/22] header: fix warning in lockdep_assert_held() Hauke Mehrtens
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=1434444988.2337.11.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=backports@vger.kernel.org \
--cc=hauke@hauke-m.de \
/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