← Back to team overview

kernel-packages team mailing list archive

[Bug 1397028] Re: Add support for the backported lts-utopic stack


This bug was fixed in the package bcmwl -

bcmwl ( precise-proposed; urgency=medium

  * New upstream release (LP: #1397028):
    - This is an official public release from Broadcom.
  * debian/patches/0013-gcc.patch
    - Fix build with recent versions of GCC. Credit
      for the patch goes to Robert Ancell.
  * debian/dkms.conf.in,
    - Drop patches for old kernels (now upstream)
    - Add support for Linux 3.17.
      Credit for the patch goes to Brian Norris.
    - Add support for Linux 3.18.
      Credit for the patch goes to Krzysztof Kolasa.

 -- Alberto Milone <alberto.milone@xxxxxxxxxxxxx>  Fri, 14 Aug 2015
12:46:43 +0200

** Changed in: bcmwl (Ubuntu Precise)
       Status: Fix Committed => Fix Released

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.

  Add support for the backported lts-utopic stack

Status in bcmwl package in Ubuntu:
Status in bcmwl source package in Precise:
  Fix Released
Status in bcmwl source package in Trusty:
  Fix Released

Bug description:
  SRU request:


   * As a result of this bug, bcmwl-kernel-source will fail to build the
  module against linux-generic-lts-utopic in Ubuntu 14.04.2.

  [Test Case]

   * Enable the trusty-proposed repository and install bcmwl-kernel-
  source (

   * Install linux-generic-lts-utopic

   * If the package installs without errors from DKMS with both the
  linux-generic and linux-generic-lts-utopic kernels, then the patches
  work correctly.

  [Regression Potential]

   * The patches that I backported from 15.04 will preserve the current
  driver behaviour on linux-generic (3.13) and linux-generic-lts-utopic
  (3.16), thanks to the use of specific macros in the code which check
  the kernel version. As a result, no regressions of any kind can be
  expected on these kernels. As a plus, support for kernels up to 3.18
  is also included.

To manage notifications about this bug go to: