Date: Wed, 13 Jan 2021 18:11:20 +0000 From: Santiago Martinez <sm@codenetworks.net> To: Hans Petter Selasky <hps@selasky.org>, FreeBSD Current <current@freebsd.org> Subject: Re: Current kernel build broken with linuxkpi? Message-ID: <c65c82cb-d084-a591-a82a-cb0114203885@codenetworks.net> In-Reply-To: <3c0d77d7-6b99-d48e-6e8a-92134b2fac7e@selasky.org> References: <712f8c5d-40ea-188d-9c66-157f68aaef30@codenetworks.net> <32038a96-f24f-3f87-f4f0-fa4eb3a56e1f@selasky.org> <2ad15f39-a267-1b6a-2f3c-65df66b29711@codenetworks.net> <b672d4de-b03f-55b4-49df-0bc1a21e0b8d@selasky.org> <3c0d77d7-6b99-d48e-6e8a-92134b2fac7e@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --8D3DSxFylY5c2ARyW3VlNT3hg2r6tltKP Content-Type: multipart/mixed; boundary="1qQjBtVFNrH62jVWHmNYLPFJAzGJuCimJ"; protected-headers="v1" From: Santiago Martinez <sm@codenetworks.net> To: Hans Petter Selasky <hps@selasky.org>, FreeBSD Current <current@freebsd.org> Message-ID: <c65c82cb-d084-a591-a82a-cb0114203885@codenetworks.net> Subject: Re: Current kernel build broken with linuxkpi? References: <712f8c5d-40ea-188d-9c66-157f68aaef30@codenetworks.net> <32038a96-f24f-3f87-f4f0-fa4eb3a56e1f@selasky.org> <2ad15f39-a267-1b6a-2f3c-65df66b29711@codenetworks.net> <b672d4de-b03f-55b4-49df-0bc1a21e0b8d@selasky.org> <3c0d77d7-6b99-d48e-6e8a-92134b2fac7e@selasky.org> In-Reply-To: <3c0d77d7-6b99-d48e-6e8a-92134b2fac7e@selasky.org> --1qQjBtVFNrH62jVWHmNYLPFJAzGJuCimJ Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US Hi HPS! thanks, that solved the issue. sorry dint realize i had to recompile the drm. Cheers Santi On 1/13/21 2:45 PM, Hans Petter Selasky wrote: > On 1/13/21 3:42 PM, Hans Petter Selasky wrote: >> On 1/13/21 3:40 PM, Santiago Martinez wrote: >>> Thanks Peter,=C2=A0 this is what i got >>> >>> root@tucho:/usr/src # git status >>> On branch main >>> Your branch is up to date with 'origin/main'. >>> >>> am i missing something? >> >> portsnap fetch update >> > > You need to update that DRM port you are using before the issue will > be fixed. > > --HPS > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" --1qQjBtVFNrH62jVWHmNYLPFJAzGJuCimJ-- --8D3DSxFylY5c2ARyW3VlNT3hg2r6tltKP Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEk06QWJzNAs9NTrFjWBFqYkyC55EFAl//N8gFAwAAAAAACgkQWBFqYkyC55HA Jw//SVHoMJDlWYQ95UtPUhMFrAAI31H9Ss8XYiziNMMhaxVOcYFw+0CnZLZTgz+oq9S4kgsPU88L 3p8S98xTaBig7o2MUv9uwpubn9uZHf1p0BcE8H3PbhGgN/v4w3ebje55vBYKjezaEAgbM/C7WBSy HjSUpejDZAbLv0ceoirTfimZIEkZxoDU8VGondJI1Mg48QV8OFRSvKW8P3jB7LhN+IPBurXUcQFk Ub2jWJR1gyIsatdXMB8rASx9RfgZB5h7JKrslvXSH0gNRz/IsKjgAR20LIwfxrmFRTFDTyLF876/ EJqYMUFYwe1/MSH1V1Qx209mLJj0ttp/HJ7OCLhw1lBdW3/Rf++DuL+UbXOzH0yBqUDVKk8sP0T0 i1B5LkpldBfrtZnYueEc/jxaF109zhUw+IQWHRHKNnKrovx3NLgUsoODrIOpUimYfH4EVIBNkLBQ iF4NBsULgXPgchrUX+XWd4DTZ8vyFUHIwwclDO55sB2L6RvpbzcmewwcgKcPc/Id82+kfHV1bYZO F4A5djMRHT7nRpFzjFhGl6W2Ki2906xN+FovWFagrm3t6Eqc5v243Od2udAsb99Q5YrMp0WDIT7V g5UOo6D9B0+9QINDKtt1hOVyb05w7ZD3AMD3ftFUolueTGxxDHJwmZJ6ZZRNow3cE4bvbVasFOxl fn0= =xrxY -----END PGP SIGNATURE----- --8D3DSxFylY5c2ARyW3VlNT3hg2r6tltKP--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c65c82cb-d084-a591-a82a-cb0114203885>