Fix several typos
PR: kern/176054 Submitted by: Christoph Mallon <christoph.mallon@gmx.de> MFC after: 3 days
This commit is contained in:
parent
d02e5a206d
commit
a164074fc4
@ -52,7 +52,7 @@ will be set to 1, if the ACL
|
||||
.Fa aclp
|
||||
points to is trivial, or 0 if it's not.
|
||||
.Pp
|
||||
ACL is trivial if it can be fully expressed as a file mode without loosing
|
||||
ACL is trivial if it can be fully expressed as a file mode without losing
|
||||
any access rules.
|
||||
For POSIX.1e ACLs, ACL is trivial if it has the three required entries,
|
||||
one for owner, one for owning group, and one for other.
|
||||
|
@ -70,7 +70,7 @@ The elements of this standard library is still not enough for more
|
||||
complicated tasks.
|
||||
In this case the provided system calls of the given operating system can be
|
||||
used.
|
||||
To not loose the portability by using these system calls, the POSIX
|
||||
To not lose the portability by using these system calls, the POSIX
|
||||
(Portable Operating System Interface) standard evolved.
|
||||
It describes what functions should be available to keep portability.
|
||||
Note, that POSIX is not a C standard, but an operating system standard
|
||||
|
@ -503,7 +503,7 @@ ata_generic_reset(device_t dev)
|
||||
mask, ostat0, ostat1);
|
||||
|
||||
/* if nothing showed up there is no need to get any further */
|
||||
/* XXX SOS is that too strong?, we just might loose devices here */
|
||||
/* XXX SOS is that too strong?, we just might lose devices here */
|
||||
ch->devices = 0;
|
||||
if (!mask)
|
||||
return;
|
||||
|
@ -137,7 +137,7 @@ uart_intr_break(void *arg)
|
||||
* much of the data we can, but otherwise flush the receiver FIFO to
|
||||
* create some breathing room. The net effect is that we avoid the
|
||||
* overrun condition to happen for the next X characters, where X is
|
||||
* related to the FIFO size at the cost of loosing data right away.
|
||||
* related to the FIFO size at the cost of losing data right away.
|
||||
* So, instead of having multiple overrun interrupts in close proximity
|
||||
* to each other and possibly pessimizing UART interrupt latency for
|
||||
* other UARTs in a multiport configuration, we create a longer segment
|
||||
@ -192,7 +192,7 @@ uart_intr_rxready(void *arg)
|
||||
* Line or modem status change (OOB signalling).
|
||||
* We pass the signals to the software interrupt handler for further
|
||||
* processing. Note that we merge the delta bits, but set the state
|
||||
* bits. This is to avoid loosing state transitions due to having more
|
||||
* bits. This is to avoid losing state transitions due to having more
|
||||
* than 1 hardware interrupt between software interrupts.
|
||||
*/
|
||||
static __inline int
|
||||
|
@ -965,7 +965,7 @@ ucom_cfg_line_state(struct usb_proc_msg *_task)
|
||||
sc->sc_pls_set = 0;
|
||||
sc->sc_pls_clr = 0;
|
||||
|
||||
/* ensure that we don't loose any levels */
|
||||
/* ensure that we don't lose any levels */
|
||||
if (notch_bits & UCOM_LS_DTR)
|
||||
sc->sc_callback->ucom_cfg_set_dtr(sc,
|
||||
(prev_value & UCOM_LS_DTR) ? 1 : 0);
|
||||
|
@ -146,7 +146,7 @@ struct ucom_super_softc {
|
||||
|
||||
struct ucom_softc {
|
||||
/*
|
||||
* NOTE: To avoid loosing level change information we use two
|
||||
* NOTE: To avoid losing level change information we use two
|
||||
* tasks instead of one for all commands.
|
||||
*
|
||||
* Level changes are transitions like:
|
||||
|
@ -333,7 +333,7 @@ fdesc_lookup(ap)
|
||||
* and the root vnode lock will be obtained afterwards (in case
|
||||
* we're looking up the fd of the root vnode), which will be the
|
||||
* opposite lock order. Vhold the root vnode first so we don't
|
||||
* loose it.
|
||||
* lose it.
|
||||
*/
|
||||
vhold(dvp);
|
||||
VOP_UNLOCK(dvp, 0);
|
||||
|
@ -148,7 +148,7 @@ stack_save(struct stack *st)
|
||||
u_register_t pc, sp;
|
||||
|
||||
if (curthread == NULL)
|
||||
panic("stack_save: curthread == NULL)");
|
||||
panic("stack_save: curthread == NULL");
|
||||
|
||||
pc = curthread->td_pcb->pcb_regs.pc;
|
||||
sp = curthread->td_pcb->pcb_regs.sp;
|
||||
|
@ -391,7 +391,7 @@ ng_hci_lp_sco_con_req(ng_hci_unit_p unit, item_p item, hook_p hook)
|
||||
|
||||
default:
|
||||
panic(
|
||||
"%s: %s - Inavalid connection state=%d\n",
|
||||
"%s: %s - Invalid connection state=%d\n",
|
||||
__func__, NG_NODE_NAME(unit->node),
|
||||
sco_con->state);
|
||||
break;
|
||||
|
@ -1011,7 +1011,7 @@ ffs_balloc_ufs2(struct vnode *vp, off_t startoffset, int size,
|
||||
* We have to sync it at the end so that the soft updates code
|
||||
* does not find any untracked changes. Although this is really
|
||||
* slow, running out of disk space is not expected to be a common
|
||||
* occurence. The error return from fsync is ignored as we already
|
||||
* occurrence. The error return from fsync is ignored as we already
|
||||
* have an error to return to the user.
|
||||
*
|
||||
* XXX Still have to journal the free below
|
||||
|
@ -789,7 +789,7 @@ lapic_handle_timer(struct trapframe *frame)
|
||||
* Don't do any accounting for the disabled HTT cores, since it
|
||||
* will provide misleading numbers for the userland.
|
||||
*
|
||||
* No locking is necessary here, since even if we loose the race
|
||||
* No locking is necessary here, since even if we lose the race
|
||||
* when hlt_cpus_mask changes it is not a big deal, really.
|
||||
*
|
||||
* Don't do that for ULE, since ULE doesn't consider hlt_cpus_mask
|
||||
|
Loading…
Reference in New Issue
Block a user