From: Johannes Berg <johannes@sipsolutions.net>
To: Thomas Graf <tgraf@suug.ch>
Cc: davem <davem@davemloft.net>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] genetlink custom attribute type
Date: Mon, 02 Oct 2006 15:56:58 +0200 [thread overview]
Message-ID: <1159797418.2655.71.camel@ux156> (raw)
In-Reply-To: <20061002134913.GB18349@postel.suug.ch>
On Mon, 2006-10-02 at 15:49 +0200, Thomas Graf wrote:
> That's not a bad idea, although it seems cleaner to just allow defining
> a callback function which gets called foreach unknown attribute.
Hm, that'd work too, but it'd force me to leave these 'unknown
attributes' at the end of the attribute space, no? Otherwise, something
with .len=0,.type=0 is sort of valid as well, not?
> As for
> generic netlink, this callback could be defined on a per command basis
> in struct genl_ops.
I'd have to look at it more closely again, I removed the custom stuff
and it's not immediately important to me at this time.
johannes
prev parent reply other threads:[~2006-10-02 13:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 7:25 [PATCH] genetlink custom attribute type Johannes Berg
2006-09-26 9:44 ` Thomas Graf
2006-09-26 10:04 ` Johannes Berg
2006-09-26 20:09 ` David Miller
2006-09-27 12:18 ` Johannes Berg
2006-10-02 13:49 ` Thomas Graf
2006-10-02 13:56 ` Johannes Berg [this message]
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=1159797418.2655.71.camel@ux156 \
--to=johannes@sipsolutions.net \
--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).