Hi Bruno, On Fri, May 29, 2020 at 7:59 PM Bruno Wolff III <bruno@xxxxxxxx> wrote: > > I occasionally submit kernel bug reports. These days one good way to > get your report looked at is to bisect a Linus kernel to find the commit > that triggered the problem. This normally takes me about a week to get > done. I have gotten fixes for bugs that affected old hardware that was in > limited use by other people. It isn't that hard to do, but kernel builds can > take a while and you need to be able to reboot for each test and there can > be limitations on when that can get done. Could you please share your workflow? I have been looking for some guidance so that I can test upstream kernels when I encounter these hardware issues. I don't need step by step instructions, I'm very comfortable compiling software, I just need some way to manage the self-compiled kernels alongside Fedora kernels without littering my system with build artifacts, and play nice with SELinux :). I typically limit any software I compile myself to /opt or $HOME; unfortunately that doesn't quite work with kernels :-p -- Suvayu Open source is the future. It sets us free. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
