staging: hv: Fixed typo in Hyper-V struct name: VMBUS_CHANNEL_PACKET_MULITPAGE_BUFFER
PATCH 1/8 staging: hv: Fixed typo in Hyper-V struct name: VMBUS_CHANNEL_PACKET_MULITPAGE_BUFFER
[ This may be a dup, didn't see the previous try ]
It seems that the VMBUS_CHANNEL_PACKET_MULITPAGE_BUFFER typedef/struct was misspelled (...MULIT.. -> ...MULTI...) so I felt compelled to fix it. This was the only change in this patch.
~~~ Steve
--- drivers/staging/hv/BlkVsc.c | 2 +- drivers/staging/hv/Channel.c | 6 +++--- drivers/staging/hv/Channel.h | 2 +- drivers/staging/hv/StorVsc.c | 2 +- drivers/staging/hv/Vmbus.c | 4 ++-- 5 files changed, 8 insertions(+), 8 deletions(-)
drivers/staging/hv/BlkVsc.c +1 -1
@@ -88,7 +88,7 @@ int BlkVscInitialize(struct hv_driver *Driver)* Divide the ring buffer data size (which is 1 page less than the ring * buffer size since that page is reserved for the ring buffer indices) * by the max request size (which is -* VMBUS_CHANNEL_PACKET_MULITPAGE_BUFFER + struct vstor_packet + u64) +* VMBUS_CHANNEL_PACKET_MULTIPAGE_BUFFER + struct vstor_packet + u64) */ storDriver->MaxOutstandingRequestsPerChannel = ((storDriver->RingBufferSize - PAGE_SIZE) /
drivers/staging/hv/Channel.c +3 -3
@@ -781,7 +781,7 @@ int VmbusChannelSendPacketMultiPageBuffer(struct vmbus_channel *Channel, void *Buffer, u32 BufferLen, u64 RequestId) { int ret; -struct VMBUS_CHANNEL_PACKET_MULITPAGE_BUFFER desc; +struct VMBUS_CHANNEL_PACKET_MULTIPAGE_BUFFER desc;u32 descSize;u32 packetLen;u32 packetLenAligned;
@@ -801,10 +801,10 @@ int VmbusChannelSendPacketMultiPageBuffer(struct vmbus_channel *Channel,ASSERT (PfnCount <=MAX_MULTIPAGE_BUFFER_COUNT );/* -* Adjust the size down since VMBUS_CHANNEL_PACKET_MULITPAGE_BUFFER is +* Adjust the size down since VMBUS_CHANNEL_PACKET_MULTIPAGE_BUFFER is * the largest size we support */ - descSize =sizeof (struct VMBUS_CHANNEL_PACKET_MULITPAGE_BUFFER ) - + descSize =sizeof (struct VMBUS_CHANNEL_PACKET_MULTIPAGE_BUFFER ) - ((MAX_MULTIPAGE_BUFFER_COUNT - PfnCount) *sizeof (u64)); packetLen = descSize + BufferLen;
drivers/staging/hv/Channel.h +1 -1
@@ -40,7 +40,7 @@ struct VMBUS_CHANNEL_PACKET_PAGE_BUFFER { } __attribute__((packed));/* The format must be the same as struct vmdata_gpa_direct */ -struct VMBUS_CHANNEL_PACKET_MULITPAGE_BUFFER { +struct VMBUS_CHANNEL_PACKET_MULTIPAGE_BUFFER {u16 Type;u16 DataOffset8;u16 Length8;
drivers/staging/hv/StorVsc.c +1 -1
@@ -824,7 +824,7 @@ int StorVscInitialize(struct hv_driver *Driver)* Divide the ring buffer data size (which is 1 page less * than the ring buffer size since that page is reserved for * the ring buffer indices) by the max request size (which is -* VMBUS_CHANNEL_PACKET_MULITPAGE_BUFFER + struct vstor_packet + u64) +* VMBUS_CHANNEL_PACKET_MULTIPAGE_BUFFER + struct vstor_packet + u64) */ storDriver->MaxOutstandingRequestsPerChannel = ((storDriver->RingBufferSize - PAGE_SIZE) /
drivers/staging/hv/Vmbus.c +2 -2
@@ -280,9 +280,9 @@ int VmbusInitialize(struct hv_driver *drv)DPRINT_INFO (VMBUS ,"+++++++ Vmbus using SINT %d +++++++" ,VMBUS_MESSAGE_SINT );DPRINT_DBG (VMBUS ,"sizeof(VMBUS_CHANNEL_PACKET_PAGE_BUFFER)=%zd, " -"sizeof(VMBUS_CHANNEL_PACKET_MULITPAGE_BUFFER)=%zd" , +"sizeof(VMBUS_CHANNEL_PACKET_MULTIPAGE_BUFFER)=%zd" ,sizeof (struct VMBUS_CHANNEL_PACKET_PAGE_BUFFER ), -sizeof (struct VMBUS_CHANNEL_PACKET_MULITPAGE_BUFFER )); +sizeof (struct VMBUS_CHANNEL_PACKET_MULTIPAGE_BUFFER )); drv->name = gDriverName;memcpy (&drv->deviceType, &gVmbusDeviceType,sizeof (struct hv_guid ));
Signature · 1 line
1.6.5.rc1
Quoted 9 lines · Steve Friedl
[ This may be a dup, didn't see the previous try ]
It seems that the
VMBUS_CHANNEL_PACKET_MULITPAGE_BUFFERtypedef/struct was misspelled (...MULIT.. -> ...MULTI...) so I felt compelled to fix it. This was the only change in this patch.~~~ Steve
Signed-off-by Steve Friedl <[email protected]>
The file, drivers/staging/hv/TODO say who to cc: for when you want to submit patches for the drivers/staging/hv/* files.
So, do you still want these patches applied? Do they apply to 2.6.32-rc3?
If not, please resend.
Heck, please resend them all again anyway, with the correct cc: in place so that all involved can review them properly.
thanks,
greg k-h