From: jamal <hadi@cyberus.ca>
To: Thomas Graf <tgraf@suug.ch>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: [RFC][GENETLINK] introduce command names
Date: Sat, 02 Dec 2006 07:11:36 -0500 [thread overview]
Message-ID: <1165061496.3564.11.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 126 bytes --]
Dave,
Same as before:
If there is no objections on this approach, please apply this patch.
Against net-2.6.20
cheers,
jamal
[-- Attachment #2: genl_cmd_name --]
[-- Type: text/plain, Size: 1338 bytes --]
[GENETLINK] introduce command names
Introduce optional command names.
While command names can be put in user space by the author of the
command, this alleviates things for the discovery process without
requiring any user space code written.
In a recent tutorial that i gave, the desire for this feature was
the highest.
Signed-off-by: Jamal Hadi Salim <hadi@cyberus.ca>
---
commit c3b92488bea3f11a6cc7c1c59101444c26ad12ce
tree 52166fb1ea684e989fef16de89c85fb9bf551bb8
parent b6ac8f41bdd2edd9d215e376efa47261e9b118a1
author Jamal Hadi Salim <hadi@cyberus.ca> Sat, 02 Dec 2006 07:08:15 -0500
committer Jamal Hadi Salim <hadi@cyberus.ca> Sat, 02 Dec 2006 07:08:15 -0500
include/net/genetlink.h | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/include/net/genetlink.h b/include/net/genetlink.h
index 7fd131c..52bc278 100644
--- a/include/net/genetlink.h
+++ b/include/net/genetlink.h
@@ -49,6 +49,7 @@ struct genl_info
/**
* struct genl_ops - generic netlink operations
* @cmd: command identifier
+ * @name: command name
* @flags: flags
* @policy: attribute validation policy
* @doit: standard command callback
@@ -58,6 +59,7 @@ struct genl_info
struct genl_ops
{
u8 cmd;
+ char name[GENL_NAMSIZ];
unsigned int flags;
struct nla_policy *policy;
int (*doit)(struct sk_buff *skb,
next reply other threads:[~2006-12-02 12:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 12:11 jamal [this message]
2006-12-04 9:28 ` [RFC][GENETLINK] introduce command names Thomas Graf
2006-12-04 13:09 ` jamal
2006-12-04 16:34 ` Thomas Graf
2006-12-04 17:49 ` jamal
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=1165061496.3564.11.camel@localhost \
--to=hadi@cyberus.ca \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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).