This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1785822 Title: linux-azure: make sure CONFIG_MLX{4,5}_INFINIBAND stays as "y" Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Bionic: Fix Released Bug description: The recent change "infiniband: mlx5: fix build errors when INFINIBAND_USER_ACCESS=m" in bionic/linux 4.15.0-31.33 caused bionic /linux-azure to revert CONFIG_MLX5_INFINIBAND to "m". Additional changes need to be included in order to keep CONFIG_MLX5_INFINIBAND=y as requested by Bug #1759656. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1785822/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp

