virtio-msg: rename EVENT_CONFIG0 to EVENT_CONFIG_EMPTY

Reviewers thought the two names were too similar.

Signed-off-by: Bill Mills <bill.mills@linaro.org>

Author: wmamills

transport-msg.tex

@@ -189,7 +189,7 @@ \subsubsection{Configuration Generation Count}
 or the response to \msgref{GET_CONFIG} which also both provide the device's
 current configuration count. The device may change any amount of data for one
 generation count increment. If the change cannot fit in one \msgref{EVENT_CONFIG}
-message, it \emph{SHOULD} be signaled to the driver via a \msgref{EVENT_CONFIG0}
+message, it \emph{SHOULD} be signaled to the driver via a \msgref{EVENT_CONFIG_EMPTY}
 message. The device \emph{MUST NOT} provide the same generation count in
 multiple \msgref{EVENT_CONFIG} messages that contain non-zero length config
 data. The driver includes its view of the current generation count in
@@ -659,7 +659,7 @@ \subsubsection{Configuration Changes During Operation}
 messages after initialization if device configuration needs to be
 changed at runtime. The device \emph{MAY} also make configuration changes at
 runtime and \emph{MUST} signal those changes with \msgref{EVENT_CONFIG} or
-\msgref{EVENT_CONFIG0} messages.
+\msgref{EVENT_CONFIG_EMPTY} messages.
 
 \subsubsection{Virtqueue Changes During Operation}
 \label{sec:Virtio Transport Options / Virtio Over Messages / Device Operation / VQueueUpdates}
@@ -738,7 +738,7 @@ \subsubsection{Overview}
 \hline
 \msgref{RESET_VQUEUE}      & 0xB  & Driver \\
 \hline
-\msgref{EVENT_CONFIG0}     & 0x40 & Device \\
+\msgref{EVENT_CONFIG_EMPTY} & 0x40 & Device \\
 \hline
 \msgref{EVENT_CONFIG}      & 0x41 & Device \\
 \hline
@@ -769,7 +769,7 @@ \subsubsection{Overview}
 \begin{itemize}
   \item \msgref{EVENT_AVAIL}
   \item \msgref{EVENT_USED}
-  \item \msgref{EVENT_CONFIG} or \msgref{EVENT_CONFIG0}
+  \item \msgref{EVENT_CONFIG} or \msgref{EVENT_CONFIG_EMPTY}
   \item \msgref{EVENT_USED}
 \end{itemize}
 
@@ -983,7 +983,7 @@ \subsubsection{Overview}
 \hline
 \end{tabular}
 
-\msgdef{EVENT_CONFIG0}
+\msgdef{EVENT_CONFIG_EMPTY}
 
 This message is sent by the virtio-msg device and there is no response.
 
@@ -995,9 +995,9 @@ \subsubsection{Overview}
 \hline
 \end{tabular}
 
-The \msgref{EVENT_CONFIG0} message is used when the extra information in 
+The \msgref{EVENT_CONFIG_EMPTY} message is used when the extra information in
 \msgref{EVENT_CONFIG} is not available. In general \msgref{EVENT_CONFIG} 
-\emph{SHOULD} be preferred to \msgref{EVENT_CONFIG0} but this is not always
+\emph{SHOULD} be preferred to \msgref{EVENT_CONFIG_EMPTY} but this is not always
 possible. If the driver side bus implementation is manufacturing notification
 based on polling intervals, it should use this message to notify the driver
 side transport layer that it should use \msgref{GET_DEVICE_STATUS} and
@@ -1268,7 +1268,7 @@ \subsubsection{Optional Requirements}
 \paragraph{Runtime Notifications}
 \begin{itemize}
   \item A device or the driver side bus \emph{MUST} send \msgref{EVENT_CONFIG}
-    or \msgref{EVENT_CONFIG0}
+    or \msgref{EVENT_CONFIG_EMPTY}
     to inform the driver of configuration of device status changes.
   \item A device or the driver side bus \emph{MUST} \msgref{EVENT_USED}
     to inform the driver of (likely) buffer completions.