From: Krishna Kumar <krkumar@us.ibm.com>
To: davem@redhat.com, kuznet@ms2.inr.ac.ru
Cc: netdev@oss.sgi.com, linux-net@vger.kernel.org
Subject: [PATCH] - Wrong use of RTM_BASE in XFRM message types.
Date: Fri, 23 May 2003 11:14:10 -0700 [thread overview]
Message-ID: <3ECE64F2.5000300@us.ibm.com> (raw)
Hi,
I am using 2.5.68 and found XFRM_MSG_BASE being defined, but RTM_BASE used for
all XFRM messages, changed it. Current mailer (hopefully) shouldn't screw up
the tabs.
Thanks,
- KK
diff -ruN linux-2.5.68.org/include/linux/xfrm.h linux-2.5.68/include/linux/xfrm.h
--- linux-2.5.68.org/include/linux/xfrm.h 2003-05-23 11:02:27.000000000 -0700
+++ linux-2.5.68/include/linux/xfrm.h 2003-05-23 11:04:02.000000000 -0700
@@ -104,17 +104,17 @@
/* Netlink configuration messages. */
#define XFRM_MSG_BASE 0x10
-#define XFRM_MSG_NEWSA (RTM_BASE + 0)
-#define XFRM_MSG_DELSA (RTM_BASE + 1)
-#define XFRM_MSG_GETSA (RTM_BASE + 2)
-
-#define XFRM_MSG_NEWPOLICY (RTM_BASE + 3)
-#define XFRM_MSG_DELPOLICY (RTM_BASE + 4)
-#define XFRM_MSG_GETPOLICY (RTM_BASE + 5)
-
-#define XFRM_MSG_ALLOCSPI (RTM_BASE + 6)
-#define XFRM_MSG_ACQUIRE (RTM_BASE + 7)
-#define XFRM_MSG_EXPIRE (RTM_BASE + 8)
+#define XFRM_MSG_NEWSA (XFRM_MSG_BASE + 0)
+#define XFRM_MSG_DELSA (XFRM_MSG_BASE + 1)
+#define XFRM_MSG_GETSA (XFRM_MSG_BASE + 2)
+
+#define XFRM_MSG_NEWPOLICY (XFRM_MSG_BASE + 3)
+#define XFRM_MSG_DELPOLICY (XFRM_MSG_BASE + 4)
+#define XFRM_MSG_GETPOLICY (XFRM_MSG_BASE + 5)
+
+#define XFRM_MSG_ALLOCSPI (XFRM_MSG_BASE + 6)
+#define XFRM_MSG_ACQUIRE (XFRM_MSG_BASE + 7)
+#define XFRM_MSG_EXPIRE (XFRM_MSG_BASE + 8)
#define XFRM_MSG_MAX (XFRM_MSG_EXPIRE+1)
next reply other threads:[~2003-05-23 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 18:14 Krishna Kumar [this message]
2003-05-26 2:48 ` [PATCH] - Wrong use of RTM_BASE in XFRM message types David S. Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3ECE64F2.5000300@us.ibm.com \
--to=krkumar@us.ibm.com \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).