[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [PATCH v2 7/7] content.tex: tighten up the definition of notification.
Repeat the language from the Terminology section and slightly reword the remaining section of the paragraph. Suggested-by: Nikos Dragazis <ndragazis@arrikto.com> Signed-off-by: Alex BennÃe <alex.bennee@linaro.org> --- content.tex | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/content.tex b/content.tex index 91735e3..d2c9a48 100644 --- a/content.tex +++ b/content.tex @@ -161,9 +161,11 @@ \subsection{Legacy Interface: A Note on Feature \section{Notifications}\label{sec:Basic Facilities of a Virtio Device / Notifications} -The notion of sending a notification (driver to device or device -to driver) plays an important role in this specification. The -modus operandi of the notifications is transport specific. +A notification is a asynchronous signal sent to either the Device or +the Driver to indicate an event has occurred. The mechanism of how a +notification is triggered (from driver to device or from device to +driver) is transport specific. Notifications play an important role in +this specification. There are three types of notifications: \begin{itemize} -- 2.20.1
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]