In message: [linux-yocto] [kernel-cache][master][yocto-5.19][yocto-5.15][PATCH] qat: fix CONFIG_CRYPTO_CCM mismatch warnings on 11/11/2022 Naveen Saini wrote:
> [NOTE]: 'CONFIG_CRYPTO_CCM' last val (m) and .config val (y) do not match > [INFO]: raw config text: > > config CRYPTO_CCM > tristate "CCM support" > select CRYPTO_CTR > select CRYPTO_HASH > select CRYPTO_AEAD > select CRYPTO_MANAGER > depends on CRYPTO > help > Support for Counter with CBC MAC. Required for IPsec. > > Config 'CRYPTO_CCM' has the following Direct dependencies > (CRYPTO_CCM=y): > CRYPTO(=y) > Parent dependencies are: > CRYPTO [y] > > [INFO]: selection details for 'CONFIG_CRYPTO_CCM': > Symbols currently y-selecting this symbol: > - CIFS > > Symbols currently m-selecting this symbol: > - MAC80211 > > Symbols currently n-selecting this symbol (no effect): > - MAC802154 > - LIB80211_CRYPT_CCMP > - RTL8192U > - RTLLIB_CRYPTO_CCMP > - SMB_SERVER > - CRYPTO_DEV_PPC4XX > - CRYPTO_DEV_NX_ENCRYPT > > [NOTE]: 'CONFIG_CRYPTO_GCM' last val (m) and .config val (y) do not match > [INFO]: raw config text: > > config CRYPTO_GCM > tristate "GCM/GMAC support" > select CRYPTO_CTR > select CRYPTO_AEAD > select CRYPTO_GHASH > select CRYPTO_NULL > select CRYPTO_MANAGER > depends on CRYPTO > help > Support for Galois/Counter Mode (GCM) and Galois > Message > Authentication Code (GMAC). Required for IPSec. > > Config 'CRYPTO_GCM' has the following Direct dependencies > (CRYPTO_GCM=y): > CRYPTO(=y) > Parent dependencies are: > CRYPTO [y] > > [INFO]: selection details for 'CONFIG_CRYPTO_GCM': > Symbols currently y-selecting this symbol: > - XFRM_ESP > - CIFS > > Symbols currently m-selecting this symbol: > - TIPC_CRYPTO > - MAC80211 > > Symbols currently n-selecting this symbol (no effect): > - TLS > - CEPH_LIB > - MACSEC > - SMB_SERVER > - CRYPTO_DEV_PPC4XX I recently added something to the kern-tools, that provide an alternate approach to solve this issue (for releases with that kern-tools change. See this commit for an example: --------------- commit edb0c33ddba78b4d3da358d814cebae074bfaaf8 Author: Bruce Ashfield <[email protected]> Date: Sun Sep 18 16:44:05 2022 -0400 config: allow mdio_bus to be y or m Signed-off-by: Bruce Ashfield <[email protected]> diff --git a/cfg/net/y_or_m_enabled.cfg b/cfg/net/y_or_m_enabled.cfg new file mode 100644 index 00000000000..2be9752212e --- /dev/null +++ b/cfg/net/y_or_m_enabled.cfg @@ -0,0 +1,2 @@ +# SPDX-License-Identifier: MIT +CONFIG_MDIO_BUS -------------- When we have options that can bounce around between built in and module, and we consider both to be valid, you can create the specially named config: y_or_m_enabled.cfg and list the options. The tools won't warn if the value is either. If you are concerned about langdale/master, this would solve the problem fully. If you are interested in older releases and this warning, then we need the patch as you have it here. Let me know, I'm ok with either approach, but it might be good to at least see if that relatively new (and lightly tested) feature can solve the problem. Bruce > > Signed-off-by: Naveen Saini <[email protected]> > --- > features/qat/qat.cfg | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/features/qat/qat.cfg b/features/qat/qat.cfg > index 2dc36225..63730abe 100644 > --- a/features/qat/qat.cfg > +++ b/features/qat/qat.cfg > @@ -3,8 +3,8 @@ > CONFIG_PREEMPT=n > CONFIG_PREEMPT_VOLUNTARY=y > CONFIG_CRYPTO_CTR=y > -CONFIG_CRYPTO_CCM=m > -CONFIG_CRYPTO_GCM=m > +CONFIG_CRYPTO_CCM=y > +CONFIG_CRYPTO_GCM=y > CONFIG_CRYPTO_XCBC=m > CONFIG_CRYPTO_VMAC=m > CONFIG_CRYPTO_CTS=m > -- > 2.25.1 > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11893): https://lists.yoctoproject.org/g/linux-yocto/message/11893 Mute This Topic: https://lists.yoctoproject.org/mt/94955051/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
