<div dir="ltr">Understood, thanks. I've submitted a ticket, could you please take a look at it ? <a href="https://bugs.launchpad.net/ubuntu/+bug/1972987">https://bugs.launchpad.net/ubuntu/+bug/1972987</a> Thanks,<div>-Vladimir</div></div> <div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, May 11, 2022 at 10:49 AM Stefan Bader <<a href="mailto:stefan.bader@canonical.com">stefan.bader@canonical.com</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 10.05.22 17:16, Tim Gardner wrote: > Config settings are only inherited by backported kernels, i.e., > focal/linux-azure-5.15 inherits configs from jammy/linux-azure. Derivatives, > such as jammy/linux-azure, have unique configs. Therefore, config changes to an > HWE kernel (which is a derivative) will require a separate patch. HWE kernels are backport kernels. -Stefan > > rtg > > On 5/10/22 08:53, Vladimir Ratnikov wrote: >> Hey Tim, >> >> Sorry for disturbing you. >> >> I was thinking that mainline kernel configuration will be inherited by HWE >> kernel, but it seems, it's not. Is it really hard to add this feature to HWE >> kernel too? >> >> Maybe I could do it, if it's possible to add just some kind of "also affects >> distribution/package"? ( If it will affect HWE of course ) >> >> What do you think about that ? >> >> Many thanks! >> >> >> >> >> On Tue, Apr 26, 2022 at 10:06 PM Tim Gardner <<a href="mailto:tim.gardner@canonical.com" target="_blank">tim.gardner@canonical.com</a> >> <mailto:<a href="mailto:tim.gardner@canonical.com" target="_blank">tim.gardner@canonical.com</a>>> wrote: >> >> >> >> On 4/26/22 08:06, Vladimir Ratnikov wrote: >> > Hey Tim! >> > >> > Thanks for submitting patch >> > <a href="https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967338" rel="noreferrer" target="_blank">https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967338</a> >> <<a href="https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967338" rel="noreferrer" target="_blank">https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967338</a>> >> > <<a href="https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967338" rel="noreferrer" target="_blank">https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967338</a> >> <<a href="https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967338" rel="noreferrer" target="_blank">https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967338</a>>> >> > >> > It was on Fix committed stage, and i've accidentally changed >> state to >> > Fix released(just missclicked) >> > But i believe, it should be done automatically or not by myself. >> Could >> > you please change it's status to Fix committed state as it was before >> > Thanks! >> > >> > BTW, just wanted to know, Fix committed says that it'll be >> available the >> > next release. Is my understanding is correct that it should be >> something >> > like Ubuntu 22.04.1 ? >> > Thanks again! >> > >> > >> >> It will be in the next kernel update due for release May 30, 2022. >> >> rtg >> -- ----------- >> Tim Gardner >> Canonical, Inc >> > </blockquote></div>