<div dir="ltr">Hey Tim!<br><br>Thanks for submitting patch<br><a href="https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967338">https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967338</a><br><br>It was on Fix committed stage, and i've accidentally changed state to Fix released(just missclicked)<br>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<br>Thanks!<br><br>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 ?<br>Thanks again!</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Apr 1, 2022 at 12:16 AM Vladimir Ratnikov <<a href="mailto:vratnikov@netgate.com">vratnikov@netgate.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Awesome, thanks! <br><br>-Vladimir</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Mar 31, 2022 at 8:51 PM Tim Gardner <<a href="mailto:tim.gardner@canonical.com" target="_blank">tim.gardner@canonical.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hmm, seems to have fallen through the cracks. Anyways, I've sent a patch <br>
which should make it into the kernel before 22.04 is released.<br>
<br>
rtg<br>
<br>
[1] <a href="https://lists.ubuntu.com/archives/kernel-team/2022-March/129085.html" rel="noreferrer" target="_blank">https://lists.ubuntu.com/archives/kernel-team/2022-March/129085.html</a><br>
<br>
On 3/31/22 09:45, Vladimir Ratnikov wrote:<br>
> Hey Tim!<br>
> <br>
> Today is the scheduled date for beta release of Ubuntu 22.04 as i know. <br>
> I don't see the option set to y in the kernel config at<br>
> <a href="https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/tree/debian.master/config/config.common.ubuntu" rel="noreferrer" target="_blank">https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/tree/debian.master/config/config.common.ubuntu</a> <br>
> <<a href="https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/tree/debian.master/config/config.common.ubuntu" rel="noreferrer" target="_blank">https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/tree/debian.master/config/config.common.ubuntu</a>>.<br>
> <br>
> Do you believe that CONFIG_SERIAL_8250_MID=y will be in 22.04?<br>
> I could create a pull request if it helps<br>
> <br>
> Thanks,<br>
> -Vladimir<br>
> <br>
> On Wed, Mar 16, 2022 at 5:48 PM Vladimir Ratnikov <<a href="mailto:vratnikov@netgate.com" target="_blank">vratnikov@netgate.com</a> <br>
> <mailto:<a href="mailto:vratnikov@netgate.com" target="_blank">vratnikov@netgate.com</a>>> wrote:<br>
> <br>
>     It would be great!<br>
> <br>
>     Thank you!<br>
> <br>
>     -Vladimir<br>
> <br>
>     On Wed, Mar 16, 2022 at 5:28 PM Tim Gardner<br>
>     <<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:<br>
> <br>
>         I'm pretty sure we can get it set for 22.04 at least. One of my<br>
>         team<br>
>         members will be working on this presently.<br>
> <br>
>         rtg<br>
> <br>
>         On 3/16/22 08:07, Vladimir Ratnikov wrote:<br>
>          > Tim, thanks for the answer!<br>
>          ><br>
>          > Does this mean that the 8250_MID module will be compiled into<br>
>         the ubuntu<br>
>          > kernel in the next release cycle?<br>
>          ><br>
>          > Thanks,<br>
>          > -Vladimir<br>
>          ><br>
>          > On Wed, Mar 16, 2022 at 3:52 PM Tim Gardner<br>
>         <<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>><br>
>          > <mailto:<a href="mailto:tim.gardner@canonical.com" target="_blank">tim.gardner@canonical.com</a><br>
>         <mailto:<a href="mailto:tim.gardner@canonical.com" target="_blank">tim.gardner@canonical.com</a>>>> wrote:<br>
>          ><br>
>          >     This seems reasonable. After all, the config change in<br>
>         Debian is 4<br>
>          >     years<br>
>          >     old.<br>
>          ><br>
>          >     rtg<br>
>          ><br>
>          >     On 3/15/22 10:36, Vladimir Ratnikov wrote:<br>
>          >      > Hello!<br>
>          >      ><br>
>          >      > At current point we have an opportunity to have<br>
>          >     CONFIG_SERIAL_8250_MID<br>
>          >      > being compiled into kernel in order to be available as<br>
>         serial<br>
>          >      > console(according to debian, there was such problem<br>
>         before and<br>
>          >     current<br>
>          >      > kernels has 'CONFIG_SERIAL_8250_MID=y' instead of<br>
>          >      > 'CONFIG_SERIAL_8250_MID=m'<br>
>          >      ><br>
>          >      > ticket:<br>
>         <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864368" rel="noreferrer" target="_blank">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864368</a><br>
>         <<a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864368" rel="noreferrer" target="_blank">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864368</a>><br>
>          >     <<a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864368" rel="noreferrer" target="_blank">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864368</a><br>
>         <<a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864368" rel="noreferrer" target="_blank">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864368</a>>><br>
>          >      ><br>
>         <<a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864368" rel="noreferrer" target="_blank">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864368</a><br>
>         <<a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864368" rel="noreferrer" target="_blank">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864368</a>><br>
>          >     <<a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864368" rel="noreferrer" target="_blank">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864368</a><br>
>         <<a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864368" rel="noreferrer" target="_blank">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864368</a>>>><br>
>          >      > patch:<br>
>          >      ><br>
>          ><br>
>         <a href="https://salsa.debian.org/kernel-team/linux/-/commit/7618511643be57b5587f66729e1c0121eb4617f6" rel="noreferrer" target="_blank">https://salsa.debian.org/kernel-team/linux/-/commit/7618511643be57b5587f66729e1c0121eb4617f6</a><br>
>         <<a href="https://salsa.debian.org/kernel-team/linux/-/commit/7618511643be57b5587f66729e1c0121eb4617f6" rel="noreferrer" target="_blank">https://salsa.debian.org/kernel-team/linux/-/commit/7618511643be57b5587f66729e1c0121eb4617f6</a>><br>
>          >   <br>
>           <<a href="https://salsa.debian.org/kernel-team/linux/-/commit/7618511643be57b5587f66729e1c0121eb4617f6" rel="noreferrer" target="_blank">https://salsa.debian.org/kernel-team/linux/-/commit/7618511643be57b5587f66729e1c0121eb4617f6</a> <<a href="https://salsa.debian.org/kernel-team/linux/-/commit/7618511643be57b5587f66729e1c0121eb4617f6" rel="noreferrer" target="_blank">https://salsa.debian.org/kernel-team/linux/-/commit/7618511643be57b5587f66729e1c0121eb4617f6</a>>><br>
>          ><br>
>          >      ><br>
>          >   <br>
>           <<a href="https://salsa.debian.org/kernel-team/linux/-/commit/7618511643be57b5587f66729e1c0121eb4617f6" rel="noreferrer" target="_blank">https://salsa.debian.org/kernel-team/linux/-/commit/7618511643be57b5587f66729e1c0121eb4617f6</a> <<a href="https://salsa.debian.org/kernel-team/linux/-/commit/7618511643be57b5587f66729e1c0121eb4617f6" rel="noreferrer" target="_blank">https://salsa.debian.org/kernel-team/linux/-/commit/7618511643be57b5587f66729e1c0121eb4617f6</a>><br>
>          >   <br>
>           <<a href="https://salsa.debian.org/kernel-team/linux/-/commit/7618511643be57b5587f66729e1c0121eb4617f6" rel="noreferrer" target="_blank">https://salsa.debian.org/kernel-team/linux/-/commit/7618511643be57b5587f66729e1c0121eb4617f6</a> <<a href="https://salsa.debian.org/kernel-team/linux/-/commit/7618511643be57b5587f66729e1c0121eb4617f6" rel="noreferrer" target="_blank">https://salsa.debian.org/kernel-team/linux/-/commit/7618511643be57b5587f66729e1c0121eb4617f6</a>>>><br>
>          >      ><br>
>          >      > So I'm wondering if there's a way of getting this<br>
>         module being<br>
>          >     compiled<br>
>          >      > into the kernel and being accepted in upstream or if<br>
>         there is<br>
>          >     something<br>
>          >      > cons about it ?<br>
>          >      ><br>
>          >      > We've rebuilt the kernel with<br>
>         'CONFIG_SERIAL_8250_MID=y' instead of<br>
>          >      > 'CONFIG_SERIAL_8250_MID=m' and haven't seen any<br>
>         problems and it<br>
>          >     worked<br>
>          >      > as expected. I believe, it'll be better for<br>
>         everyone having this<br>
>          >     module<br>
>          >      > to be the part of kernel.<br>
>          >      ><br>
>          >      ><br>
>          >      > Thanks!<br>
>          >      > -Vladimir<br>
>          >      ><br>
>          ><br>
>          >     --<br>
>          >     -----------<br>
>          >     Tim Gardner<br>
>          >     Canonical, Inc<br>
>          ><br>
> <br>
>         -- <br>
>         -----------<br>
>         Tim Gardner<br>
>         Canonical, Inc<br>
> <br>
<br>
-- <br>
-----------<br>
Tim Gardner<br>
Canonical, Inc<br>
</blockquote></div>
</blockquote></div>