Public bug reported:

[SRU Justification]

= Impact =

We want to add some driver code which exists in the primary kernel
source but will not get included unless specifically asked for. As long
as there are no drivers using this, there is no user-visible change.

= Impact =

This will be done by adding a new config option which gets turned on via
build setup rules. The default will be off.

= Testcase =

As long as there are no consumers changes can only be seen by inspecting
the build logs (if even that).

= Regression Potential =

This prepares for future consumers. At this stage either the build will
fail completely or pass and in that case the produced kernel binaries
are the same as they were before.

** Affects: linux (Ubuntu)
     Importance: Medium
     Assignee: Stefan Bader (smb)
         Status: In Progress

** Affects: linux (Ubuntu Focal)
     Importance: Medium
     Assignee: Stefan Bader (smb)
         Status: In Progress

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Changed in: linux (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Focal)
       Status: New => In Progress

** Changed in: linux (Ubuntu Focal)
     Assignee: (unassigned) => Stefan Bader (smb)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1912789

Title:
  Add support for selective build of special drivers

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress

Bug description:
  [SRU Justification]

  = Impact =

  We want to add some driver code which exists in the primary kernel
  source but will not get included unless specifically asked for. As
  long as there are no drivers using this, there is no user-visible
  change.

  = Impact =

  This will be done by adding a new config option which gets turned on
  via build setup rules. The default will be off.

  = Testcase =

  As long as there are no consumers changes can only be seen by
  inspecting the build logs (if even that).

  = Regression Potential =

  This prepares for future consumers. At this stage either the build
  will fail completely or pass and in that case the produced kernel
  binaries are the same as they were before.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912789/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to