summaryrefslogtreecommitdiffstats
path: root/lib/libc/stdlib/realpath.c
diff options
context:
space:
mode:
authormiod <miod@openbsd.org>2010-11-20 20:33:21 +0000
committermiod <miod@openbsd.org>2010-11-20 20:33:21 +0000
commit916e928b748d205ed7dd2b5402633c775908f1b7 (patch)
tree2174c5ea99d26c4db47bb15d4825f29a84e3d1a2 /lib/libc/stdlib/realpath.c
parentMake sure we do not overrun the memory ranges array, should the booter (diff)
downloadwireguard-openbsd-916e928b748d205ed7dd2b5402633c775908f1b7.tar.xz
wireguard-openbsd-916e928b748d205ed7dd2b5402633c775908f1b7.zip
This is a first step towards getting rid of avail_start and avail_end in the
kernel, currently limited to low-hanging fruit: these variables were used by bus_dma to specify the range in which to allocate memory, back when uvm_pglistalloc() was stupid and would not walk the vm_physseg[]. Nowadays, except on some platforms for early initialization, these variables are not used, or do not need to be global variables. Therefore: - remove `extern' declarations of avail_start and avail_end (or close cousins, such as arm physical_start and physical_end) from files which no longer need to use them. - make them local variables whenever possible. - remove them when they are assigned to but no longer used.
Diffstat (limited to 'lib/libc/stdlib/realpath.c')
0 files changed, 0 insertions, 0 deletions