public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Eric Biggers <ebiggers@kernel.org>, linux-wireless@vger.kernel.org
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [PATCH wireless-next v2 0/6] Consolidate Michael MIC code into cfg80211
Date: Wed, 08 Apr 2026 08:32:12 +0200	[thread overview]
Message-ID: <56798292be29f3e76e88c837d41eff0cb9f8b36a.camel@sipsolutions.net> (raw)
In-Reply-To: <20260408030651.80336-1-ebiggers@kernel.org>

On Tue, 2026-04-07 at 20:06 -0700, Eric Biggers wrote:
> 
> Changed in v2:
> 
>     - Added preparatory patch to fix a bisection hazard.
> 
>     - Moved michael_mic() to cfg80211 so that ipw2x00 doesn't have to
>       start depending on mac80211.

Thanks.

>     - Adjusted the 'fips_enabled' error messages, and updated the commit
>       messages to clarify that ath11k and ath12k don't actually work at
>       all in FIPS mode but that these patches don't aim to fix that.

:)

> Eric Biggers (6):
>   wifi: ipw2x00: Rename michael_mic() to libipw_michael_mic()
>   wifi: mac80211, cfg80211: Export michael_mic() and move it to cfg80211
>   wifi: ath11k: Use michael_mic() from cfg80211
>   wifi: ath12k: Use michael_mic() from cfg80211
>   wifi: ipw2x00: Use michael_mic() from cfg80211
>   crypto: Remove michael_mic from crypto_shash API

So five out of six patches are wireless, should I apply the crypto one
too?

johannes

  parent reply	other threads:[~2026-04-08  6:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-08  3:06 [PATCH wireless-next v2 0/6] Consolidate Michael MIC code into cfg80211 Eric Biggers
2026-04-08  3:06 ` [PATCH wireless-next v2 1/6] wifi: ipw2x00: Rename michael_mic() to libipw_michael_mic() Eric Biggers
2026-04-08  3:06 ` [PATCH wireless-next v2 2/6] wifi: mac80211, cfg80211: Export michael_mic() and move it to cfg80211 Eric Biggers
2026-04-08  3:06 ` [PATCH wireless-next v2 3/6] wifi: ath11k: Use michael_mic() from cfg80211 Eric Biggers
2026-04-08  3:06 ` [PATCH wireless-next v2 4/6] wifi: ath12k: " Eric Biggers
2026-04-08  3:06 ` [PATCH wireless-next v2 5/6] wifi: ipw2x00: " Eric Biggers
2026-04-08  3:06 ` [PATCH wireless-next v2 6/6] crypto: Remove michael_mic from crypto_shash API Eric Biggers
2026-04-08  8:09   ` Herbert Xu
2026-04-08  6:32 ` Johannes Berg [this message]
2026-04-08  7:13   ` [PATCH wireless-next v2 0/6] Consolidate Michael MIC code into cfg80211 Eric Biggers
2026-04-08  7:28     ` Johannes Berg

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=56798292be29f3e76e88c837d41eff0cb9f8b36a.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=ebiggers@kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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