The Kernel Team mailing list is open to the public. If anyone is
interested in our patches/fixes/misc kernel ramblings, they are more
than welcome to sign up. The mailing list is also Googleable:
http://tinyurl.com/2vh6thw. I believe the first link are our ramblings
and the second is relevant to th
I understand that it's easier just to follow the kernel mailing list to
find out what the patches are and track if they are merged or not (what
I did), but my concern was more how could an external person (not from
ubuntu kernel team) could find and test/grab the fixes?
Happens a lot that people s
> This is released already.
Normally bugs are moved from "Fix Committed" -> "Fixed Released" by the
Launchpad Janitor. This is a bit of an odd case whereby the bug report
was raised after the patches were sent for review. As there was no bug
report open, the "BugLink: http://bugs.launchpad.net/bug
This is released already.
Lee, it would also help if you could point the address of the patches,
or saying where they were sent (with the hash), this can help tracking
the issue. Just saying the issue is fixed means nothing from the test
perspective.
The patches:
http://kernel.ubuntu.com/git?p=ub
** Changed in: linux-ti-omap (Ubuntu)
Status: In Progress => Fix Committed
--
USB and Ethernet are broken on the Beagle XM
https://bugs.launchpad.net/bugs/608095
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
This issue is fixed.
I'm just waiting for the patches to be applied to our kernel.
The patches are also being sent upstream by a third party.
--
USB and Ethernet are broken on the Beagle XM
https://bugs.launchpad.net/bugs/608095
You received this bug notification because you are a member of Ubu
