d/freebsd-nq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

There is nothing more embarresing than having three goes at correcting

Browse Source 
typos in the same paragraph.  s/in in/in/

Submitted by:	iedowse
This commit is contained in:
Peter Wemm 2001-08-27 05:18:12 +00:00
parent 76cb0cadf1
commit 9d170964e4
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
sys/amd64/amd64/locore.S
View File

@ -78,7 +78,7 @@
* NOTE: PTDpde, PTmap, and PTD are being defined as address symbols.
* In C you access them directly, and not with a '*'. Storage is not being
* allocated. They will magically address the correct locations in KVM
* which C will treat as normal variables of the type they are defined in in
* which C will treat as normal variables of the type they are defined in
* machine/pmap.h, i.e. PTDpde = XX ; to set a PDE entry, NOT *PTDpde = XX;
*/
.globl PTmap,PTD,PTDpde

2
sys/amd64/amd64/locore.s
View File

@ -78,7 +78,7 @@
* NOTE: PTDpde, PTmap, and PTD are being defined as address symbols.
* In C you access them directly, and not with a '*'. Storage is not being
* allocated. They will magically address the correct locations in KVM
* which C will treat as normal variables of the type they are defined in in
* which C will treat as normal variables of the type they are defined in
* machine/pmap.h, i.e. PTDpde = XX ; to set a PDE entry, NOT *PTDpde = XX;
*/
.globl PTmap,PTD,PTDpde

2
sys/i386/i386/locore.s
View File

@ -78,7 +78,7 @@
* NOTE: PTDpde, PTmap, and PTD are being defined as address symbols.
* In C you access them directly, and not with a '*'. Storage is not being
* allocated. They will magically address the correct locations in KVM
* which C will treat as normal variables of the type they are defined in in
* which C will treat as normal variables of the type they are defined in
* machine/pmap.h, i.e. PTDpde = XX ; to set a PDE entry, NOT *PTDpde = XX;
*/
.globl PTmap,PTD,PTDpde