On čtvrtek 17. března 2016 11:09 Takashi Iwai wrote:
On Thu, 17 Mar 2016 09:01:02 +0100,
Where we're at it: this leads me a question how to handle Evergreen kernel bug reports at best.
The most imporant message is: Evergreen is a community project run by volunteers on best effort basis. Thus nobody should feel obliged to work on evergreen bugs.
Strictly speaking, Evergreen kernel isn't identical with SLE12-SP1's one.
True. The code base diff is minimal (even if bigger than I would like now because of an attempt to revive 32-bit kernel-xen and some fixes of non-SMP builds (ppc)). More important difference is that evergreen-13.1 has more features enabled and more modules built so some of the bugs reported may be about code not used in SLE12-SP1. On the other hand, so far most of the issues reported would actually affect SLE12-SP1 as well and some of them uncovered issues that could hit even enterprise customers (e.g. bsc#970249). My plan is to look at the bug reports first, make sure information needed to start is provided, do some initial analysis, see if I can resolve it myself and if the report is interesting from SLE12-SP1 point of view and based on that, decide whether to ask another developer for help. Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org