[ovs-dev] [PATCH v2 6/6] NetlinkBuf.c: Minor fix for lines exceeding 79 chars

[Ankur Sharma]

Signed-off-by: Ankur Sharma <ankursharma at vmware.com>
Tested-by: Ankur Sharma <ankursharma at vmware.com>
Reported-at: https://github.com/openvswitch/ovs-issues/issues/37
Acked-by: Eitan Eliahu <eliahue at vmware.com>
Acked-by: Alin Gabriel Serdean <aserdean at cloudbasesolutions.com>

---
 datapath-windows/ovsext/Netlink/NetlinkBuf.c | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/datapath-windows/ovsext/Netlink/NetlinkBuf.c b/datapath-windows/ovsext/Netlink/NetlinkBuf.c
index 590c803..ba10d83 100644
--- a/datapath-windows/ovsext/Netlink/NetlinkBuf.c
+++ b/datapath-windows/ovsext/Netlink/NetlinkBuf.c
@@ -71,7 +71,8 @@
 static __inline VOID
 _NlBufCopyAtTailUnsafe(PNL_BUFFER nlBuf, PCHAR data, UINT32 len);
 static __inline VOID
-_NlBufCopyAtOffsetUnsafe(PNL_BUFFER nlBuf, PCHAR data, UINT32 len, UINT32 offset);
+_NlBufCopyAtOffsetUnsafe(PNL_BUFFER nlBuf, PCHAR data,
+                         UINT32 len, UINT32 offset);
 
 /*
  * --------------------------------------------------------------------------
@@ -134,7 +135,8 @@ done:
  * NlBufCopyAtHead --
  *
  *    Copies the data to the head of the buffer.
- *    It can be seen as special case of NlBufCopyAtOffset with input offset zero.
+ *    It can be seen as special case of NlBufCopyAtOffset with input
+ *    offset zero.
  * --------------------------------------------------------------------------
  */
 BOOLEAN
@@ -330,7 +332,8 @@ _NlBufCopyAtTailUnsafe(PNL_BUFFER nlBuf, PCHAR data, UINT32 len)
  * --------------------------------------------------------------------------
  */
 static __inline VOID
-_NlBufCopyAtOffsetUnsafe(PNL_BUFFER nlBuf, PCHAR data, UINT32 len, UINT32 offset)
+_NlBufCopyAtOffsetUnsafe(PNL_BUFFER nlBuf, PCHAR data,
+                         UINT32 len, UINT32 offset)
 {
     PCHAR dest = NULL;
 
-- 
1.9.1