Date: Mon, 24 Jul 2023 22:31:24 -0600 From: Warner Losh <imp@bsdimp.com> To: scsi@freebsd.org, "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Heads up: s/u_intXX_t/uintXX_t/ in sys/cam Message-ID: <CANCZdfoMJ=Cs%2B1P6as%2BwOtCEU3ib%2B43Cf=wAzJrsNuN0WHc-TA@mail.gmail.com> In-Reply-To: <CANCZdfqXJ%2BoTH8ApMfAdVn4Vmn7CbXqQeHrzqMYbsx1FQxB9sg@mail.gmail.com> References: <CANCZdfqXJ%2BoTH8ApMfAdVn4Vmn7CbXqQeHrzqMYbsx1FQxB9sg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--00000000000022acbf060148342f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I have just pushed this update into -current. It compiles and boots for me. It should be a giant nop. I plan on MFCing this in a few days unless there's unanticipated turbulence. I have not updated the SIM drivers because most of the u_intXX_t use in these drivers are not related to CAM interfaces. And many of these drivers are vendor code, to various degrees. I think this is the ideal time: Before the 14 branch, when all I need to do is merge to 13 since 12 is about to go out of support. There will never be a better time. Please let me know if I missed anything. or there are problems. Warner On Fri, Jul 7, 2023 at 3:12=E2=80=AFPM Warner Losh <imp@bsdimp.com> wrote: > I plan on finally biting the bullet and moving to the standard uintXX_t. > > I plan on doing this next week, before we branch 14. > > I also plan on MFC'ing these changes (or rather running the same script > and tagging that commit as a MFC). > > This has been talked about forever, and now seems like we have a good lul= l > in things to do it. > > Comments? > > Warner > > --00000000000022acbf060148342f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><div>I have just pushed this update into = -current. It compiles and boots for me. It should be a giant nop. I plan on= MFCing this in a few days unless there's unanticipated turbulence.</di= v><div><br></div><div>I have not updated the SIM drivers because most of th= e u_intXX_t use in these drivers are not related to CAM interfaces. And man= y of these drivers are vendor code, to various degrees.</div><div><br></div= ><div>I think this is the ideal time: Before the 14 branch, when all I need= to do is merge to 13 since 12 is about to go out of support. There will ne= ver be a better time.<br></div><div><br></div><div>Please let me know if I = missed anything. or there are problems.<br></div><div><br></div><div>Warner= <br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gm= ail_attr">On Fri, Jul 7, 2023 at 3:12=E2=80=AFPM Warner Losh <<a href=3D= "mailto:imp@bsdimp.com">imp@bsdimp.com</a>> wrote:<br></div><blockquote = class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol= id rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>I plan on final= ly biting the bullet and moving to the standard uintXX_t.</div><div><br></d= iv><div>I plan on doing this next week, before we branch 14.</div><div><br>= </div><div>I also plan on=C2=A0 MFC'ing these changes (or rather runnin= g the same script and tagging that commit as a MFC).</div><div><br></div><d= iv>This has been talked about forever, and now seems like we have a good lu= ll in things to do it.</div><div><br></div><div>Comments?</div><div><br></d= iv><div>Warner</div><div><br></div></div> </blockquote></div></div> --00000000000022acbf060148342f--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfoMJ=Cs%2B1P6as%2BwOtCEU3ib%2B43Cf=wAzJrsNuN0WHc-TA>