From: Stephen Hemminger <sthem...@microsoft.com>

Lots of little spelling mistakes.

Signed-off-by: Stephen Hemminger <sthem...@microsoft.com>
---
 drivers/hv/channel.c    | 16 ++++++++--------
 drivers/hv/connection.c |  2 +-
 drivers/hv/hv_kvp.c     |  6 +++---
 drivers/hv/vmbus_drv.c  |  2 +-
 include/linux/hyperv.h  | 16 ++++++++--------
 5 files changed, 21 insertions(+), 21 deletions(-)

diff --git a/drivers/hv/channel.c b/drivers/hv/channel.c
index 56dd261..4cf5c33 100644
--- a/drivers/hv/channel.c
+++ b/drivers/hv/channel.c
@@ -331,7 +331,7 @@ static int create_gpadl_header(void *kbuffer, u32 size,
                         * Gpadl is u32 and we are using a pointer which could
                         * be 64-bit
                         * This is governed by the guest/host protocol and
-                        * so the hypervisor gurantees that this is ok.
+                        * so the hypervisor guarantees that this is ok.
                         */
                        for (i = 0; i < pfncurr; i++)
                                gpadl_body->pfn[i] = slow_virt_to_phys(
@@ -377,7 +377,7 @@ nomem:
 }
 
 /*
- * vmbus_establish_gpadl - Estabish a GPADL for the specified buffer
+ * vmbus_establish_gpadl - Establish a GPADL for the specified buffer
  *
  * @channel: a channel
  * @kbuffer: from kmalloc or vmalloc
@@ -530,7 +530,7 @@ static int vmbus_close_internal(struct vmbus_channel 
*channel)
        /*
         * In case a device driver's probe() fails (e.g.,
         * util_probe() -> vmbus_open() returns -ENOMEM) and the device is
-        * rescinded later (e.g., we dynamically disble an Integrated Service
+        * rescinded later (e.g., we dynamically disable an Integrated Service
         * in Hyper-V Manager), the driver's remove() invokes vmbus_close():
         * here we should skip most of the below cleanup work.
         */
@@ -662,7 +662,7 @@ int vmbus_sendpacket_ctl(struct vmbus_channel *channel, 
void *buffer,
                                  &signal, lock);
 
        /*
-        * Signalling the host is conditional on many factors:
+        * Signaling the host is conditional on many factors:
         * 1. The ring state changed from being empty to non-empty.
         *    This is tracked by the variable "signal".
         * 2. The variable kick_q tracks if more data will be placed
@@ -758,7 +758,7 @@ int vmbus_sendpacket_pagebuffer_ctl(struct vmbus_channel 
*channel,
        /* Setup the descriptor */
        desc.type = VM_PKT_DATA_USING_GPA_DIRECT;
        desc.flags = flags;
-       desc.dataoffset8 = descsize >> 3; /* in 8-bytes grandularity */
+       desc.dataoffset8 = descsize >> 3; /* in 8-bytes granularity */
        desc.length8 = (u16)(packetlen_aligned >> 3);
        desc.transactionid = requestid;
        desc.rangecount = pagecount;
@@ -780,7 +780,7 @@ int vmbus_sendpacket_pagebuffer_ctl(struct vmbus_channel 
*channel,
                                  &signal, lock);
 
        /*
-        * Signalling the host is conditional on many factors:
+        * Signaling the host is conditional on many factors:
         * 1. The ring state changed from being empty to non-empty.
         *    This is tracked by the variable "signal".
         * 2. The variable kick_q tracks if more data will be placed
@@ -848,7 +848,7 @@ int vmbus_sendpacket_mpb_desc(struct vmbus_channel *channel,
        /* Setup the descriptor */
        desc->type = VM_PKT_DATA_USING_GPA_DIRECT;
        desc->flags = VMBUS_DATA_PACKET_FLAG_COMPLETION_REQUESTED;
-       desc->dataoffset8 = desc_size >> 3; /* in 8-bytes grandularity */
+       desc->dataoffset8 = desc_size >> 3; /* in 8-bytes granularity */
        desc->length8 = (u16)(packetlen_aligned >> 3);
        desc->transactionid = requestid;
        desc->rangecount = 1;
@@ -907,7 +907,7 @@ int vmbus_sendpacket_multipagebuffer(struct vmbus_channel 
*channel,
        /* Setup the descriptor */
        desc.type = VM_PKT_DATA_USING_GPA_DIRECT;
        desc.flags = VMBUS_DATA_PACKET_FLAG_COMPLETION_REQUESTED;
-       desc.dataoffset8 = descsize >> 3; /* in 8-bytes grandularity */
+       desc.dataoffset8 = descsize >> 3; /* in 8-bytes granularity */
        desc.length8 = (u16)(packetlen_aligned >> 3);
        desc.transactionid = requestid;
        desc.rangecount = 1;
diff --git a/drivers/hv/connection.c b/drivers/hv/connection.c
index fcf8a02..b06faee 100644
--- a/drivers/hv/connection.c
+++ b/drivers/hv/connection.c
@@ -88,7 +88,7 @@ static int vmbus_negotiate_version(struct 
vmbus_channel_msginfo *msginfo,
         * This has been the behavior pre-win8. This is not
         * perf issue and having all channel messages delivered on CPU 0
         * would be ok.
-        * For post win8 hosts, we support receiving channel messagges on
+        * For post win8 hosts, we support receiving channel messages on
         * all the CPUs. This is needed for kexec to work correctly where
         * the CPU attempting to connect may not be CPU 0.
         */
diff --git a/drivers/hv/hv_kvp.c b/drivers/hv/hv_kvp.c
index cb1a916..71b8ed7 100644
--- a/drivers/hv/hv_kvp.c
+++ b/drivers/hv/hv_kvp.c
@@ -379,7 +379,7 @@ kvp_send_key(struct work_struct *dummy)
         * the max lengths specified. We will however, reserve room
         * for the string terminating character - in the utf16s_utf8s()
         * function we limit the size of the buffer where the converted
-        * string is placed to HV_KVP_EXCHANGE_MAX_*_SIZE -1 to gaurantee
+        * string is placed to HV_KVP_EXCHANGE_MAX_*_SIZE -1 to guarantee
         * that the strings can be properly terminated!
         */
 
@@ -589,8 +589,8 @@ response_done:
  * This callback is invoked when we get a KVP message from the host.
  * The host ensures that only one KVP transaction can be active at a time.
  * KVP implementation in Linux needs to forward the key to a user-mde
- * component to retrive the corresponding value. Consequently, we cannot
- * respond to the host in the conext of this callback. Since the host
+ * component to retrieve the corresponding value. Consequently, we cannot
+ * respond to the host in the context of this callback. Since the host
  * guarantees that at most only one transaction can be active at a time,
  * we stash away the transaction state in a set of global variables.
  */
diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c
index e82f7e1..8ae2ed7 100644
--- a/drivers/hv/vmbus_drv.c
+++ b/drivers/hv/vmbus_drv.c
@@ -787,7 +787,7 @@ static void vmbus_isr(void)
                /*
                 * Our host is win8 or above. The signaling mechanism
                 * has changed and we can directly look at the event page.
-                * If bit n is set then we have an interrup on the channel
+                * If bit n is set then we have an interrupt on the channel
                 * whose id is n.
                 */
                handled = true;
diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h
index f46159d..54b7fef 100644
--- a/include/linux/hyperv.h
+++ b/include/linux/hyperv.h
@@ -239,7 +239,7 @@ struct vmbus_channel_offer {
 
                /*
                 * Pipes:
-                * The following sructure is an integrated pipe protocol, which
+                * The following structure is an integrated pipe protocol, which
                 * is implemented on top of standard user-defined data. Pipe
                 * clients have MAX_PIPE_USER_DEFINED_BYTES left for their own
                 * use.
@@ -773,13 +773,13 @@ struct vmbus_channel {
         * Support for sub-channels. For high performance devices,
         * it will be useful to have multiple sub-channels to support
         * a scalable communication infrastructure with the host.
-        * The support for sub-channels is implemented as an extention
+        * The support for sub-channels is implemented as an extension
         * to the current infrastructure.
         * The initial offer is considered the primary channel and this
         * offer message will indicate if the host supports sub-channels.
-        * The guest is free to ask for sub-channels to be offerred and can
+        * The guest is free to ask for sub-channels to be offered and can
         * open these sub-channels as a normal "primary" channel. However,
-        * all sub-channels will have the same type and instance guids as the
+        * all sub-channels will have the same type and instance GUID's as the
         * primary channel. Requests sent on a given channel will result in a
         * response on the same channel.
         */
@@ -839,11 +839,11 @@ struct vmbus_channel {
        enum hv_signal_policy  signal_policy;
        /*
         * On the channel send side, many of the VMBUS
-        * device drivers explicity serialize access to the
+        * device drivers explicitly serialize access to the
         * outgoing ring buffer. Give more control to the
         * VMBUS device drivers in terms how to serialize
-        * accesss to the outgoing ring buffer.
-        * The default behavior will be to aquire the
+        * access to the outgoing ring buffer.
+        * The default behavior will be to acquire the
         * ring lock to preserve the current behavior.
         */
        bool acquire_ring_lock;
@@ -911,7 +911,7 @@ void vmbus_set_chn_rescind_callback(struct vmbus_channel 
*channel,
 struct vmbus_channel *vmbus_get_outgoing_channel(struct vmbus_channel 
*primary);
 
 /*
- * Check if sub-channels have already been offerred. This API will be useful
+ * Check if sub-channels have already been offered. This API will be useful
  * when the driver is unloaded after establishing sub-channels. In this case,
  * when the driver is re-loaded, the driver would have to check if the
  * subchannels have already been established before attempting to request
-- 
2.9.3

_______________________________________________
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

Reply via email to