Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 24 Feb 2023 04:30:48 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 266315] linuxkpi panic after recent updates (13.1-STABLE #0 stable/13-9cbba5950: Wed Sep  7 23:42:41 CEST 2022)
Message-ID:  <bug-266315-227-3wAJGtPUiX@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-266315-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-266315-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D266315

--- Comment #49 from Paul Dufresne <dufresnep@zoho.com> ---
(In reply to Paul Dufresne from comment #47)

I did mislead you!

Don't do:
cp
work/xf86-video-intel-31486f40f8e8f8923ca0799aea84b58799754564/src/sna/kgem=
.c
work/xf86-video-intel-31486f40f8e8f8923ca0799aea84b58799754564/src/sna/kgem=
.c.orig
nano
work/xf86-video-intel-31486f40f8e8f8923ca0799aea84b58799754564/src/sna/kgem=
.c

because the .orig file was existing... and so the file was patched

by doing this step I am overwriting the patch... erasing it, at the next st=
ep:
make makepatch (which will compare .c.orig with .c file).

Do that only when the .orig file did not exist.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-266315-227-3wAJGtPUiX>