Date: Wed, 1 Oct 2025 12:41:01 -0700 From: Gleb Smirnoff <glebius@freebsd.org> To: Mateusz Guzik <mjguzik@gmail.com> Cc: Renato Botelho <garga@freebsd.org>, Mateusz Guzik <mjg@freebsd.org>, src-committers@freebsd.org, dev-commits-src-all@freebsd.org, dev-commits-src-main@freebsd.org Subject: Re: git: 08f06aa1b4fb - main - vfs: retire the VCALL macro Message-ID: <aN2DzR4J_Z3iH67C@cell.glebi.us> In-Reply-To: <CAGudoHHPO6anvVqAncZBhkuk1nuPBgxaEuW=%2B4Edq1QmuQ8Lag@mail.gmail.com> References: <202509270401.58R41A7b014829__21824.1523530864$1758945716$gmane$org@gitrepo.freebsd.org> <85c486e1-6fde-4f4a-b4ce-bfbec7bb693f@FreeBSD.org> <CAGudoHHPO6anvVqAncZBhkuk1nuPBgxaEuW=%2B4Edq1QmuQ8Lag@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 01, 2025 at 09:01:57PM +0200, Mateusz Guzik wrote: M> > FYI, this commit along with retirement of NULLVP and VREF broke M> > open-vm-kmod build on current. I wonder if there are move ports that M> > could be affected. M> > M> M> I could bump __freebsd_version for it, but what you can do is simply M> not use the old stuff on any supported branch. It is responsibility of src committer who broke a port to take care of it or at least be helpful to fix its build. -- Gleb Smirnoff
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aN2DzR4J_Z3iH67C>