Luiz Capitulino <lcapitul...@redhat.com> writes: > 1. s/These are devices are/These devices are > 2. s/Thefirst/The first > 3. s/, Guest should/. Guest should > > Signed-off-by: Luiz Capitulino <lcapitul...@redhat.com> > --- > virtio-spec.lyx | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-)
Thanks... I changed ", Guest" to ". The guest", and re-entered the changes by hand to get change tracking. Thanks, Rusty. > > diff --git a/virtio-spec.lyx b/virtio-spec.lyx > index 6e188d0..7e4ce71 100644 > --- a/virtio-spec.lyx > +++ b/virtio-spec.lyx > @@ -116,7 +116,7 @@ description "Peripheral Component Interconnect; a common > device bus. See\\\\htt > \end_inset > > devices. > - These are devices are found in > + These devices are found in > \emph on > virtual > \emph default > @@ -1558,7 +1558,7 @@ name "sub:Feature-Bits" > \end_layout > > \begin_layout Standard > -Thefirst configuration field indicates the features that the device supports. > +The first configuration field indicates the features that the device > supports. > The bits are allocated as follows: > \end_layout > > @@ -2919,7 +2919,7 @@ For each ring, guest should then disable interrupts by > writing VRING_AVAIL_F_NO_ > INTERRUPT flag in avail structure, if required. > It can then process used ring entries finally enabling interrupts by > clearing > the VRING_AVAIL_F_NO_INTERRUPT flag or updating the EVENT_IDX field in > - the available structure, Guest should then execute a memory barrier, and > + the available structure. Guest should then execute a memory barrier, and > then recheck the ring empty condition. > This is necessary to handle the case where, after the last check and before > enabling interrupts, an interrupt has been suppressed by the device: > -- > 1.8.1.4 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
