Corvin Köhne 99902b1c52 linuxkpi/dmi: don't match exactly on DMI_MATCH ... Linux has two defines to check dmi data. DMI_MATCH checks if the dmi string includes substr. DMI_EXACT_MATCH checks if the dmi string exactly matches substr. Compat layer should have the same behaviour. The new definition of dmi_strmatch shouldn't break any driver. A driver would break if it uses the highest bit of the slot field. Nevertheless, linux uses the same definition and FreeBSD uses dmi_field values as slot which are lower than 128. Sponsored by: Beckhoff Automation GmbH & Co. KG MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D35395		2022-06-03 16:20:45 +02:00
..
freebsd32	Finish cpuset_getaffinity() after f35093f8	2022-05-28 20:53:08 +03:00
ia32	Retire sv_transtrap	2022-05-20 14:54:03 +03:00
lindebugfs	lindebugfs: The Linux file operations use negative return values in the kernel.	2022-03-11 17:41:33 +01:00
linprocfs	linprocfs: Add /proc/vm/max_map_count	2022-05-31 11:42:06 +03:00
linsysfs	linsysfs: plug set-but-not-used vars.	2022-03-31 23:49:26 +03:00
linux	linux(4): Return EINVAL when the clockid has invalid bits are set	2022-05-31 11:46:15 +03:00
linuxkpi/common	linuxkpi/dmi: don't match exactly on DMI_MATCH	2022-06-03 16:20:45 +02:00
x86bios	Mark more nodes as CTLFLAG_MPSAFE or CTLFLAG_NEEDGIANT (17 of many)	2020-02-26 14:26:36 +00:00