Skip to contentSkip to conversation

remove leading space in linux/skbuff.h

PATCH In review Olaf Hering 2 participants 5 messages Sep 18, 2004 – Sep 22, 2004

Subsystems (2)
Networking Network drivers
lore
Share & tools
lore

Olaf Hering

author
#0 lore raw

PATCH 1/1 remove leading space in linux/skbuff.h

unifdef complains about the leading space.

Signed-off-by Olaf Hering <[email protected]>
include/linux/skbuff.h +1 -1
diff -purN linux-2.6.8/include/linux/skbuff.h linux-2.6.8.xxx/include/linux/skbuff.h
@@ -271,7 +271,7 @@ struct sk_buff {
 #ifdef CONFIG_NET_CLS_ACT
 	__u32           tc_verd;               /* traffic control verdict */
 	__u32           tc_classid;            /* traffic control classid */
- #endif
+#endif
 
 #endif
Signature · 3 lines
USB is for mice, FireWire is for men!

sUse lINUX ag, nÜRNBERG
author
#1 lore raw
Quoted 2 lines · Olaf Hering

unifdef complains about the leading space.

maybe the whole content can be in #ifdef __KERNEL__

Signed-off-by Olaf Hering <[email protected]>
include/linux/skbuff.h +2 -2
diff -purN linux-2.6.8/include/linux/skbuff.h linux-2.6.8.xxx/include/linux/skbuff.h
@@ -13,6 +13,7 @@
 
 #ifndef _LINUX_SKBUFF_H
 #define _LINUX_SKBUFF_H
+#ifdef __KERNEL__
 
 #include <linux/config.h>
 #include <linux/kernel.h>

@@ -271,7 +272,7 @@ struct sk_buff {
 #ifdef CONFIG_NET_CLS_ACT
 	__u32           tc_verd;               /* traffic control verdict */
 	__u32           tc_classid;            /* traffic control classid */
- #endif
+#endif
 
 #endif
 

@@ -285,7 +286,6 @@ struct sk_buff {
 				*end;
 };
 
-#ifdef __KERNEL__
 /*
  *	Handling routines are only of interest to the kernel
  */
Signature · 3 lines
USB is for mice, FireWire is for men!

sUse lINUX ag, nÜRNBERG
maintainer
#2 lore raw
In reply to Olaf Hering

Olaf, please resend your patches as attachments or something like that, there are "=20" all over your patch when I save the email and try to use it as a patch.

Thanks.

author
#3 lore raw
Quoted 4 lines · David S. Miller

Olaf, please resend your patches as attachments or something like that, there are "=20" all over your patch when I save the email and try to use it as a patch.

David,
msgid [email protected] and the reply doesnt contain such an encoding.

Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

Signature · 3 lines
USB is for mice, FireWire is for men!

sUse lINUX ag, nÜRNBERG
maintainer
#4 lore raw
Quoted 7 lines · On Wed, 22 Sep 2004 10:42:08 +0200 Olaf Hering <[email protected]> wrote:

David,
msgid [email protected] and the reply doesnt contain such an encoding.

Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

Well, there they were when I saved the message text to a file using sylpheed.

Thanks for the attachment, I'll integrate your patches.