src/sys/arm/versatile, branch releng/13.3FreeBSD source treehttps://cgit-dev.freebsd.org/src/atom?h=releng%2F13.32023-08-23T17:43:27Zsys: Remove $FreeBSD$: one-line sh pattern2023-08-23T17:43:27ZWarner Loshimp@FreeBSD.org2023-08-22T01:31:56Zurn:sha1:5510f79042fbd543de55807d0da7f8a2b8be2f89
Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
Similar commit in current:
(cherry picked from commit 031beb4e239b)
sys: Remove $FreeBSD$: one-line .c pattern2023-08-23T17:43:25ZWarner Loshimp@FreeBSD.org2023-08-22T01:31:27Zurn:sha1:3bc80996974a61a4223eae4c1ccd47b6ee32a48a
Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/
Similar commit in current:
(cherry picked from commit 685dc743dc3b)
sys: Remove $FreeBSD$: two-line .h pattern2023-08-23T17:43:20ZWarner Loshimp@FreeBSD.org2023-08-22T01:31:02Zurn:sha1:f8167e0404dab9ffeaca95853dd237ab7c587f82
Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/
Similar commit in current:
(cherry picked from commit 95ee2897e98f)
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD2023-07-25T15:13:49ZWarner Loshimp@FreeBSD.org2023-05-10T15:40:58Zurn:sha1:caa41f641755c935b036e17440a3b49329c904ed
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch
up to that fact and revert to their recommended match of BSD-2-Clause.
Discussed with: pfg
MFC After: 3 days
Sponsored by: Netflix
(cherry picked from commit 4d846d260e2b9a3d4d0a701462568268cbfe7a5b)
Remove the pre-ARMv6 and pre-INTRNG code.2020-11-29T08:40:12ZMichal Melounmmel@FreeBSD.org2020-11-29T08:40:12Zurn:sha1:5c2967f66fbfba57e246e683430982e08b1127aa
ARM has required ARMV6+ and INTRNg for some time now, so remove
always false #ifdefs and unconditionally do always true #ifdefs.
arm: clean up empty lines in .c and .h files2020-09-01T21:17:24ZMateusz Guzikmjg@FreeBSD.org2020-09-01T21:17:24Zurn:sha1:654548838bebbda54247e122f932b01c3d5c51b3Add KERNEL_PANICKED macro for use in place of direct panicstr tests2020-01-12T06:07:54ZMateusz Guzikmjg@FreeBSD.org2020-01-12T06:07:54Zurn:sha1:879e0604ee6ac0ded87f6754141e7af25f4b7d5aKill off dummy kbd drivers2019-12-20T16:22:14ZKyle Evanskevans@FreeBSD.org2019-12-20T16:22:14Zurn:sha1:db41cd0e062561c71684f68dbf81f903b73ca282
As far as I can tell, these are an artifact of times when linker sets
couldn't be empty, otherwise the kernel build would fail due to unresolved
symbols. hselasky fixed this in r268138, and I've audited the kbd portions
to make sure nothing would blow up due to the empty linker set and
successfully compiled+ran a kernel with no keyboard support at all.
Kill them off now since they're no longer required.
MFC after: 1 week
VERSATILEPB: Unbreak after r3557962019-12-20T15:28:40ZKyle Evanskevans@FreeBSD.org2019-12-20T15:28:40Zurn:sha1:2dfc696ef1138196e7283b72d9fae203d0dfac69
r355796 provided genkbd_get_fkeystr/genkbd_diag private and the default for
get_fkeystr/diag if these members are NULL. Follow suit here.
kbd drivers: use kbdd_* indirection for diag invocation2019-12-16T01:37:03ZKyle Evanskevans@FreeBSD.org2019-12-16T01:37:03Zurn:sha1:4434de96438e10b3a771b760a0ceab7e2564fb5f
These invocations were directly calling enkbd_diag(), rather than
indirection back through kbdd_diag/kbdsw. While they're functionally
equivent, invoking kbdd_diag where feasible (i.e. not in a diag
implementation) makes it easier to visually identify locking needs in these
other drivers.