committer filter by committer.
@path/to/ filter by path in repository.
committer@path/to/ filter by committer AND path in repository.
abdef0123 filter by commit's SHA hash.
rNNN filter by SVN revision.
rNNN-rMMM filter by SVN revisions range (inclusive).
Multiple filters can be specified separated by spaces or comas in which case they'll be combined using OR operator.
|d4accf60||imp||Sept. 23, 2022, 9:07 p.m.||arm64: don't loop forever if first option in kern.cfg.order not available
strchr returns a pointer to the ',', so if the first option in the list isn't available, we need to step over the , to look at the next option. So if kern.cfg.order="acpi,fdt" and we have no acpi, we'd loop forever with order=',fdt'. Sponsored by: Netflix Reviewed by: andrew, jhb Differential Revision: https://reviews.freebsd.org/D36682cgit
|8232a1ed||brooks||Sept. 23, 2022, 8:20 p.m.||cpuset(9): Refer to CPU_SETSIZE not MAXCPU
The maximum CPU number of a cpuset_t is determined by CPU_SETSIZE. In the kernel this is MAXCPU, but in userspace it is CPU_MAXSIZE unless CPU_SETSIZE is defined before including sys/_cpuset.h. CPU_MAXSIZE is 256 and in userspace MAXCPU is generally 1 because it being set to a larger MD value is gated on SMP being defined (not generally the case in userspace). Reported by: Nathaniel Wesley Filardo <firstname.lastname@example.org> Reviewed by: cem, jhb MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D36679cgit
|62a7dae4||imp||Sept. 23, 2022, 3:53 p.m.||release: Use standard mount points for arm MBR boot images
Traditionally, we've used /boot/msdos for the MBR mount point for the SD images that we produced. For GPT and bsdinstall, we've used /boot/efi. Migrate to using /boot/efi for MBR as well and add a /boot/msdos -> /boot/efi symlink for compatibility (which may disappear before 14.0, but will remain on the stable branches). When we first created the arm images, there was no EFI booting and the FAT partion on an MBR image was used to hold the firmware, uboot.bin, SoC config files and ubldr. When we transitioned to uboot with EFI, we put the loader files in the same partition. Later we standardized on /boot/efi at about the same time we added GPT support to the RE produced images. We left the MRB case as /boot/msdos for legacy reasons and since it wasn't always EFI. Later, we dropped support of non-EFI booting on the RE produced images, so the duality of /boot/msdos diminished even more. Since so little secondary meaning remains, putting it all in /boot/efi standardizes the location and reflects the RE images better as using efi-only booting. In addition, always label the msdosfs partion 'efi'. While a small misnomer on some systems that store other files in the ESP, it was requested in review for more consistency for similar reasons to the mountpoint rename. There was no way to have an 'alias' or 'second label' here, so this breaks compatibility. Since the images are self-contained, this was judged to be an acceptable change. Sponsored by: Netflix Reviewed by: manu, allanjude, emaste, gjb Differential Revision: https://reviews.freebsd.org/D36635cgit
|9ba957e4||andrew||Sept. 23, 2022, 2:28 p.m.||Fix the spelling of interrupt in the GICv3 driver
Reported by: jrtc27 Sponsored by: Innovate UKcgit
|7a5d47de||andrew||Sept. 23, 2022, 2:28 p.m.||Make adding children consistant in the GICv3 drivers
Reorder statements to make them consistant between the ACPI and FDT GICv3 attachments. Reported by: jrtc27 Sponsored by: Innovate UKcgit
|839374bb||andrew||Sept. 23, 2022, 2:28 p.m.||Teach the GICv3 driver to translate memory ranges
As with the GICv1/2 driver teach the GICv3 driver to translate memory ranges of children. This allows us to create a common bus_alloc_resource implementation for bot hACPI and FDT attachments. Sponsored by: The FreeBSD Foundationcgit
|bdc9ece9||andrew||Sept. 23, 2022, 2:28 p.m.||Move the GICv3 bus_print_child function to the parent
This should be common for both ACPI and FDT. Move this to the common part of the driver. Sponsored by: The FreeBSD Foundationcgit
|6fc6896c||andrew||Sept. 23, 2022, 2:28 p.m.||Add bus_get_resource_list functions to the GICv3 driver
This will be used to reduce code duplication between the ACPI and FDT attachments. Sponsored by: The FreeBSD Foundationcgit
|f5027467||hselasky||Sept. 23, 2022, 11:42 a.m.||ibcore: The use of IN_LOOPBACK() now requires a valid VNET context.
Make sure the VNET is set before using this macro. Fixes: efe58855f3ea2cfc24cb705aabce3bc0fe1fb6d5 PR: 266054 MFC after: 1 week Sponsored by: NVIDIA Networkingcgit
|f968cb14||pauamma||Sept. 23, 2022, 8:32 a.m.||Track removal of Tokenring and FDDI media types from devd.cc.|
|00d8a28f||cy||Sept. 22, 2022, 10:38 p.m.||ipfilter/libipf: printpool_live() consumer ignores return code
The single consumer of printpool_live() ignores the return code. Avoid wasting resources on this. MFC after: 2 weekscgit
|5568c8b2||cy||Sept. 22, 2022, 10:38 p.m.||ipfilter/ippool: Return error code when listing a pool fails
When an internal or other error occurs during the listing of a pool, return an error code when extiting ippool(8). Printing an error to stderr without returning an error code is useless in shell scripts. MFC after: 2 weekscgit
|7531c434||cy||Sept. 22, 2022, 10:38 p.m.||ipfilter/ippool: Dump a copy of ippool in ippool.conf format
Add an ippool(8) option to dump a copy of the inm-memory ippool tables in an ippool(5) format so that it can be reloaded using ippool -f. MFC after: 2 weekscgit
|7e58c8aa||maxim||Sept. 22, 2022, 10:35 p.m.||iwlwifi.4: typo fixed
|6bddde30||jhb||Sept. 22, 2022, 10:10 p.m.||Bump __FreeBSD_version for pmap_unmap*() and kmem_*() API changes.
Sponsored by: DARPAcgit