Searched hist:1.210 (Results 1 - 25 of 234) sorted by relevance
| /src/usr.bin/make/unit-tests/ | ||
| H A D | varmod-remember.mk | 1.6 Sun Mar 14 17:27:27 GMT 2021 rillig make: do not expand the variable name in the ':_' modifier This edge case had been so obscure that even discovering this takes quite some time and requires reading the source code of make. The manual page doesn't document whether the variable name is expanded or not, it doesn't even give an example. When this obscure modifier was initially added in var.c 1.210 from 2017-01-30, Var_Set always expanded the variable name once, and there was no way around it. Therefore this expansion has probably been unintentional. |
| /src/sys/dev/pcmcia/ | ||
| H A D | pcmciadevs.h | 1.210 Sun Feb 27 15:29:37 GMT 2005 perry branches: 1.210.2; regen 1.210 Sun Feb 27 15:29:37 GMT 2005 perry branches: 1.210.2; regen |
| H A D | pcmciadevs_data.h | 1.210 Sun Feb 27 15:29:37 GMT 2005 perry branches: 1.210.2; regen 1.210 Sun Feb 27 15:29:37 GMT 2005 perry branches: 1.210.2; regen |
| /src/sys/kern/ | ||
| H A D | kern_sysctl.c | 1.210 Wed Aug 15 00:07:34 GMT 2007 ad branches: 1.210.2; 1.210.8; 1.210.10; 1.210.14; Changes to make ktrace LKM friendly and reduce ifdef KTRACE. Proposed on tech-kern. 1.210 Wed Aug 15 00:07:34 GMT 2007 ad branches: 1.210.2; 1.210.8; 1.210.10; 1.210.14; Changes to make ktrace LKM friendly and reduce ifdef KTRACE. Proposed on tech-kern. 1.210 Wed Aug 15 00:07:34 GMT 2007 ad branches: 1.210.2; 1.210.8; 1.210.10; 1.210.14; Changes to make ktrace LKM friendly and reduce ifdef KTRACE. Proposed on tech-kern. 1.210 Wed Aug 15 00:07:34 GMT 2007 ad branches: 1.210.2; 1.210.8; 1.210.10; 1.210.14; Changes to make ktrace LKM friendly and reduce ifdef KTRACE. Proposed on tech-kern. 1.210 Wed Aug 15 00:07:34 GMT 2007 ad branches: 1.210.2; 1.210.8; 1.210.10; 1.210.14; Changes to make ktrace LKM friendly and reduce ifdef KTRACE. Proposed on tech-kern. |
| H A D | vfs_bio.c | 1.210 Thu Sep 11 09:14:46 GMT 2008 hannken branches: 1.210.2; 1.210.4; 1.210.6; 1.210.10; nestiobuf_setup(): Initialize b_dev from master buffer. 1.210 Thu Sep 11 09:14:46 GMT 2008 hannken branches: 1.210.2; 1.210.4; 1.210.6; 1.210.10; nestiobuf_setup(): Initialize b_dev from master buffer. 1.210 Thu Sep 11 09:14:46 GMT 2008 hannken branches: 1.210.2; 1.210.4; 1.210.6; 1.210.10; nestiobuf_setup(): Initialize b_dev from master buffer. 1.210 Thu Sep 11 09:14:46 GMT 2008 hannken branches: 1.210.2; 1.210.4; 1.210.6; 1.210.10; nestiobuf_setup(): Initialize b_dev from master buffer. 1.210 Thu Sep 11 09:14:46 GMT 2008 hannken branches: 1.210.2; 1.210.4; 1.210.6; 1.210.10; nestiobuf_setup(): Initialize b_dev from master buffer. |
| H A D | kern_proc.c | 1.212 Sat Apr 14 14:26:20 GMT 2018 kamil branches: 1.212.2; Don't set errno ESRCH for empty result of KINFO_PROC[2] Restore the previous behavior as it's prefered. This new behavior was introduced in 1.210. Code should check for length of the result. Requested by <mlelstv> 1.210 Sun Mar 11 15:13:05 GMT 2018 kre Make a comment meaningful. ie: s/Ditto/what it was copying/ (more or less) That is, there was a comment "Ditto" - which once upon a time, was used to indicate the the previous comment applied here as well. Time passed, and software mutated, and the previous comment was unfortunately sacrificed. Poor little Ditto was left all alone. Noticed while doing some software archaeology. |
| H A D | kern_time.c | 1.210 Tue Dec 08 04:09:38 GMT 2020 thorpej branches: 1.210.2; A couple of tweaks to the previous re-factor: - Some of what was defined as "generic itimer" behavior turned out to be ptimer-specific. As such, everything related to the "fired timer queue" is now specific to ptimers, and the queue and softint handle fields of itimer_ops are not needed. - Split itimer_fini() into 2 parts: itimer_poision() marks the timer as dead and attempts to cancel it. itimer_fini() is then just responsible for freeing itimer resources and releasing the lock. They are split into two parts, as ptimers require an addition processing step between those two operations, but other kinds of itimers do not necessarily require that. - Export a few more itimer-related symbols that other itimer types will need. Riding previous kernel version bump since there are no external uses of this code since the version bump that accompanied the original change. 1.210 Tue Dec 08 04:09:38 GMT 2020 thorpej branches: 1.210.2; A couple of tweaks to the previous re-factor: - Some of what was defined as "generic itimer" behavior turned out to be ptimer-specific. As such, everything related to the "fired timer queue" is now specific to ptimers, and the queue and softint handle fields of itimer_ops are not needed. - Split itimer_fini() into 2 parts: itimer_poision() marks the timer as dead and attempts to cancel it. itimer_fini() is then just responsible for freeing itimer resources and releasing the lock. They are split into two parts, as ptimers require an addition processing step between those two operations, but other kinds of itimers do not necessarily require that. - Export a few more itimer-related symbols that other itimer types will need. Riding previous kernel version bump since there are no external uses of this code since the version bump that accompanied the original change. |
| /src/sys/arch/sparc/sparc/ | ||
| H A D | cpu.c | 1.210 Sat Feb 16 18:17:36 GMT 2008 he branches: 1.210.6; 1.210.8; 1.210.10; 1.210.12; Remove a now-superfluous & after the change to spc_lwplock in sched.h. 1.210 Sat Feb 16 18:17:36 GMT 2008 he branches: 1.210.6; 1.210.8; 1.210.10; 1.210.12; Remove a now-superfluous & after the change to spc_lwplock in sched.h. 1.210 Sat Feb 16 18:17:36 GMT 2008 he branches: 1.210.6; 1.210.8; 1.210.10; 1.210.12; Remove a now-superfluous & after the change to spc_lwplock in sched.h. 1.210 Sat Feb 16 18:17:36 GMT 2008 he branches: 1.210.6; 1.210.8; 1.210.10; 1.210.12; Remove a now-superfluous & after the change to spc_lwplock in sched.h. 1.210 Sat Feb 16 18:17:36 GMT 2008 he branches: 1.210.6; 1.210.8; 1.210.10; 1.210.12; Remove a now-superfluous & after the change to spc_lwplock in sched.h. |
| H A D | autoconf.c | 1.210 Thu Jun 16 04:17:49 GMT 2005 briggs branches: 1.210.2; Rename 'ncpus' to 'sparc_ncpus' to avoid shadow warnings in m.i. code. Also sprinkle an __UNVOLATILE() for sparc. n.b. sparc64 'cpus' should probably be renamed to 'cpu_info_list' to match i386 et al. 1.210 Thu Jun 16 04:17:49 GMT 2005 briggs branches: 1.210.2; Rename 'ncpus' to 'sparc_ncpus' to avoid shadow warnings in m.i. code. Also sprinkle an __UNVOLATILE() for sparc. n.b. sparc64 'cpus' should probably be renamed to 'cpu_info_list' to match i386 et al. |
| /src/sys/dev/pci/ | ||
| H A D | pciide.c | 1.210 Fri Sep 17 23:04:02 GMT 2004 enami branches: 1.210.4; 1.210.6; Whitespace nit. 1.210 Fri Sep 17 23:04:02 GMT 2004 enami branches: 1.210.4; 1.210.6; Whitespace nit. 1.210 Fri Sep 17 23:04:02 GMT 2004 enami branches: 1.210.4; 1.210.6; Whitespace nit. |
| /src/sys/ufs/lfs/ | ||
| H A D | lfs_vnops.c | 1.210 Sun Jul 29 13:31:15 GMT 2007 ad branches: 1.210.4; 1.210.6; 1.210.8; 1.210.10; It's not a good idea for device drivers to modify b_flags, as they don't need to understand the locking around that field. Instead of setting B_ERROR, set b_error instead. b_error is 'owned' by whoever completes the I/O request. 1.210 Sun Jul 29 13:31:15 GMT 2007 ad branches: 1.210.4; 1.210.6; 1.210.8; 1.210.10; It's not a good idea for device drivers to modify b_flags, as they don't need to understand the locking around that field. Instead of setting B_ERROR, set b_error instead. b_error is 'owned' by whoever completes the I/O request. 1.210 Sun Jul 29 13:31:15 GMT 2007 ad branches: 1.210.4; 1.210.6; 1.210.8; 1.210.10; It's not a good idea for device drivers to modify b_flags, as they don't need to understand the locking around that field. Instead of setting B_ERROR, set b_error instead. b_error is 'owned' by whoever completes the I/O request. 1.210 Sun Jul 29 13:31:15 GMT 2007 ad branches: 1.210.4; 1.210.6; 1.210.8; 1.210.10; It's not a good idea for device drivers to modify b_flags, as they don't need to understand the locking around that field. Instead of setting B_ERROR, set b_error instead. b_error is 'owned' by whoever completes the I/O request. 1.210 Sun Jul 29 13:31:15 GMT 2007 ad branches: 1.210.4; 1.210.6; 1.210.8; 1.210.10; It's not a good idea for device drivers to modify b_flags, as they don't need to understand the locking around that field. Instead of setting B_ERROR, set b_error instead. b_error is 'owned' by whoever completes the I/O request. |
| /src/sys/dev/usb/ | ||
| H A D | uhci.c | 1.210 Wed Aug 15 04:00:33 GMT 2007 kiyohara branches: 1.210.2; 1.210.6; * splsoftusb, IPL_SOFTUSB, and IPL_HARDUSB defines in usbdi.h -> the current names are confusing (didn't change other drivers) * fix invalid memory access in usbd_transfer (kern/24636) -> needed for this driver * fix USB HC detach race condition (kern/32011) -> main patch needed for this driver, sc_dying changes in other drivers not necessary but seem right to me Patch from Matthew Orgass. http://mail-index.netbsd.org/tech-kern/2007/06/26/0001.html 1.210 Wed Aug 15 04:00:33 GMT 2007 kiyohara branches: 1.210.2; 1.210.6; * splsoftusb, IPL_SOFTUSB, and IPL_HARDUSB defines in usbdi.h -> the current names are confusing (didn't change other drivers) * fix invalid memory access in usbd_transfer (kern/24636) -> needed for this driver * fix USB HC detach race condition (kern/32011) -> main patch needed for this driver, sc_dying changes in other drivers not necessary but seem right to me Patch from Matthew Orgass. http://mail-index.netbsd.org/tech-kern/2007/06/26/0001.html 1.210 Wed Aug 15 04:00:33 GMT 2007 kiyohara branches: 1.210.2; 1.210.6; * splsoftusb, IPL_SOFTUSB, and IPL_HARDUSB defines in usbdi.h -> the current names are confusing (didn't change other drivers) * fix invalid memory access in usbd_transfer (kern/24636) -> needed for this driver * fix USB HC detach race condition (kern/32011) -> main patch needed for this driver, sc_dying changes in other drivers not necessary but seem right to me Patch from Matthew Orgass. http://mail-index.netbsd.org/tech-kern/2007/06/26/0001.html |
| /src/sys/miscfs/procfs/ | ||
| H A D | procfs_vnops.c | 1.210 Mon Feb 24 20:47:41 GMT 2020 ad branches: 1.210.4; v_interlock -> vmobjlock 1.210 Mon Feb 24 20:47:41 GMT 2020 ad branches: 1.210.4; v_interlock -> vmobjlock |
| /src/sys/arch/hp300/hp300/ | ||
| H A D | machdep.c | 1.210 Thu Dec 10 14:13:49 GMT 2009 matt branches: 1.210.2; Change u_long to vaddr_t/vsize_t in exec code where appropriate (mostly involves setregs and vmcmds). Should result in no code differences. 1.210 Thu Dec 10 14:13:49 GMT 2009 matt branches: 1.210.2; Change u_long to vaddr_t/vsize_t in exec code where appropriate (mostly involves setregs and vmcmds). Should result in no code differences. |
| /src/lib/libm/ | ||
| H A D | Makefile | 1.210 Sat Apr 27 23:04:32 GMT 2019 kamil branches: 1.210.2; Add a C99 symbol to libm: nexttowardl It's an alias for an already existing symbol nextafterl. Patch obtained from <mgorny> Detected by the LLVM buildbot breakage in tests. 1.210 Sat Apr 27 23:04:32 GMT 2019 kamil branches: 1.210.2; Add a C99 symbol to libm: nexttowardl It's an alias for an already existing symbol nextafterl. Patch obtained from <mgorny> Detected by the LLVM buildbot breakage in tests. |
| /src/distrib/sets/lists/xcomp/ | ||
| H A D | mi | 1.210 Sun Jul 21 00:15:13 GMT 2019 rjs branches: 1.210.2; Add ftcolor.h to build from freetype2. 1.210 Sun Jul 21 00:15:13 GMT 2019 rjs branches: 1.210.2; Add ftcolor.h to build from freetype2. |
| /src/usr.bin/make/ | ||
| H A D | meta.c | 1.210 Sun Jun 02 15:31:26 GMT 2024 rillig branches: 1.210.2; make: sync VarEvalMode constant names with their debug log names 1.210 Sun Jun 02 15:31:26 GMT 2024 rillig branches: 1.210.2; make: sync VarEvalMode constant names with their debug log names |
| /src/usr.bin/ | ||
| H A D | Makefile | 1.210 Wed Aug 08 14:13:46 GMT 2012 christos branches: 1.210.2; exclude programs for MKRUMP = no 1.210 Wed Aug 08 14:13:46 GMT 2012 christos branches: 1.210.2; exclude programs for MKRUMP = no |
| /src/sys/arch/sparc64/sparc64/ | ||
| H A D | locore.s | 1.210 Sat Feb 11 17:57:32 GMT 2006 cdi branches: 1.210.2; 1.210.4; 1.210.6; ANSIfication: u_intN_t -> uintN_t, use ANSI function declarations/definitions instead of K&R ones. 1.210 Sat Feb 11 17:57:32 GMT 2006 cdi branches: 1.210.2; 1.210.4; 1.210.6; ANSIfication: u_intN_t -> uintN_t, use ANSI function declarations/definitions instead of K&R ones. 1.210 Sat Feb 11 17:57:32 GMT 2006 cdi branches: 1.210.2; 1.210.4; 1.210.6; ANSIfication: u_intN_t -> uintN_t, use ANSI function declarations/definitions instead of K&R ones. 1.210 Sat Feb 11 17:57:32 GMT 2006 cdi branches: 1.210.2; 1.210.4; 1.210.6; ANSIfication: u_intN_t -> uintN_t, use ANSI function declarations/definitions instead of K&R ones. |
| /src/sys/ufs/ext2fs/ | ||
| H A D | ext2fs_vfsops.c | 1.210 Sun Jul 30 14:23:54 GMT 2017 riastradh branches: 1.210.2; kmem_xyz(sizeof(struct foo)) --> kmem_xyz(sizeof(*foo)) No change to amd64 binary. 1.210 Sun Jul 30 14:23:54 GMT 2017 riastradh branches: 1.210.2; kmem_xyz(sizeof(struct foo)) --> kmem_xyz(sizeof(*foo)) No change to amd64 binary. |
| /src/sys/ufs/ufs/ | ||
| H A D | ufs_vnops.c | 1.210 Mon Jun 04 20:13:47 GMT 2012 riastradh branches: 1.210.2; Kill the IN_RENAME in-core inode flag in ufs and ext2fs. Now that rename works we need not to wave this sort of voodoo at it. ok dholland 1.210 Mon Jun 04 20:13:47 GMT 2012 riastradh branches: 1.210.2; Kill the IN_RENAME in-core inode flag in ufs and ext2fs. Now that rename works we need not to wave this sort of voodoo at it. ok dholland |
| /src/sys/miscfs/genfs/ | ||
| H A D | genfs_vnops.c | 1.210 Sat Sep 05 16:30:12 GMT 2020 riastradh branches: 1.210.6; Round of uvm.h cleanup. The poorly named uvm.h is generally supposed to be for uvm-internal users only. - Narrow it to files that actually need it -- mostly files that need to query whether curlwp is the pagedaemon, which should maybe be exposed by an external header. - Use uvm_extern.h where feasible and uvm_*.h for things not exposed by it. We should split up uvm_extern.h but this will serve for now to reduce the uvm.h dependencies. - Use uvm_stat.h and #ifdef UVMHIST uvm.h for files that use UVMHIST(ubchist), since ubchist is declared in uvm.h but the reference evaporates if UVMHIST is not defined, so we reduce header file dependencies. - Make uvm_device.h and uvm_swap.h independently includable while here. ok chs@ 1.210 Sat Sep 05 16:30:12 GMT 2020 riastradh branches: 1.210.6; Round of uvm.h cleanup. The poorly named uvm.h is generally supposed to be for uvm-internal users only. - Narrow it to files that actually need it -- mostly files that need to query whether curlwp is the pagedaemon, which should maybe be exposed by an external header. - Use uvm_extern.h where feasible and uvm_*.h for things not exposed by it. We should split up uvm_extern.h but this will serve for now to reduce the uvm.h dependencies. - Use uvm_stat.h and #ifdef UVMHIST uvm.h for files that use UVMHIST(ubchist), since ubchist is declared in uvm.h but the reference evaporates if UVMHIST is not defined, so we reduce header file dependencies. - Make uvm_device.h and uvm_swap.h independently includable while here. ok chs@ |
| /src/sys/net/ | ||
| H A D | route.c | 1.210 Fri Jun 01 07:13:35 GMT 2018 ozaki-r branches: 1.210.2; Fix _rt_free via rtrequest(RTM_DELETE) hangs in rt_timer handlers A rt_timer handler is passed a rtentry with an extra reference that avoids the rtentry is accidentally released. So rt_timer handers must release the reference of a passed rtentry by themselves (but they didn't). 1.210 Fri Jun 01 07:13:35 GMT 2018 ozaki-r branches: 1.210.2; Fix _rt_free via rtrequest(RTM_DELETE) hangs in rt_timer handlers A rt_timer handler is passed a rtentry with an extra reference that avoids the rtentry is accidentally released. So rt_timer handers must release the reference of a passed rtentry by themselves (but they didn't). |
| /src/sys/arch/x86/x86/ | ||
| H A D | cpu.c | 1.210 Mon Apr 22 23:07:47 GMT 2024 andvar branches: 1.210.2; Surround full mp_cpu_start() method with NLAPIC > 0 guard. Initialization is based on x86_ipi* functions, which are implemented only when lapic flag is enabled. 1.210 Mon Apr 22 23:07:47 GMT 2024 andvar branches: 1.210.2; Surround full mp_cpu_start() method with NLAPIC > 0 guard. Initialization is based on x86_ipi* functions, which are implemented only when lapic flag is enabled. |
| /src/sys/arch/mips/mips/ | ||
| H A D | locore.S | 1.210 Wed Jan 24 03:13:36 GMT 2018 maya branches: 1.210.2; Clarify this is a load delay nop. 1.210 Wed Jan 24 03:13:36 GMT 2018 maya branches: 1.210.2; Clarify this is a load delay nop. |
Completed in 315 milliseconds