ubuntu-bugcontrol team mailing list archive

[Christopher Penalver <christopher.m.penalver@xxxxxxxxx>]

Dear Ubuntu Kernel Team / Ubuntu Bug Control:

Hello. While triaging wireless related linux (Ubuntu) bug reports, a
seemingly common misconception is that when an original reporter tests
the mainline kernel, they refuse to test compat-wireless or upstream
compat-wireless due to the following common response, "I already
tested the mainline kernel". This seems in error, as the mainline
kernel provided by the Ubuntu Kernel team
https://wiki.ubuntu.com/Kernel/MainlineBuilds does not include patches
in linux-next, correct? If so, it seems prudent to further clarify
this in the following Ubuntu debugging articles to prevent this
misconception:
https://wiki.ubuntu.com/Kernel/MainlineBuilds
https://wiki.ubuntu.com/Kernel/LinuxWireless

I came to this conclusion due to the following resources:

Definition of linux-next as per upstream
https://backports.wiki.kernel.org/index.php/Main_Page .

As per https://wiki.ubuntu.com/Kernel/MainlineBuilds :
>"We currently build five sets of mainline kernels. All formal tags from Linus' tree and from the stable trees, plus:
    the tip of the master branch from Linus' tree daily,
    the tip of the drm-next head of Dave Airlie's linux repository daily,
    the tip of the drm-intel-next head of Keith Packard's linux
repository daily,
    the tip of the master branch of the debloat-testing tree daily,
    tags from the combined v2.6.32.x.y tree (by StefanBader) which is
v2.6.32.x with DRM from 2.6.33.y.
This makes these kernels closer to the Lucid kernels which are based
on 2.6.32 kernels with DRM backported from the 2.6.33 series."

As per http://linux.f-seidel.de/linux-next/pmwiki/pmwiki.php?n=Linux-next.FAQ :
>"When and how will linux-next get into linus tree?
I'll cite a email between Paolo Ciarrocchi and Stephen Rothwell to answer this:
> Is Linus going to pull from that tree as soon as we reach -rc0 or this
> is just a tree
> used for testing what will be pushed to Linus as soon as the two weeks
> merge window
> open?
The intention is the latter.  I hope to help people sort out some of the
conflicts and cross subsystem issues before we get into the merge window
and the code gets into Linus' tree.
Andrew Morton also hopes that the linux-next tree may get more testing
that the -mm tree did if we can stop it having to many regressions by
only including the less experimental code that is destined for the next
kernel release."

What do you think?

Thank you for your time and consideration in this matter and I look
forward to your response.

-- 
Christopher M. Penalver
E-Mail: christopher.m.penalver@xxxxxxxxx
https://launchpad.net/~penalvch