From: Thomas Graf <tgraf@suug.ch>
To: jamal <hadi@cyberus.ca>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [RFC][GENETLINK] move command capabilities to flags
Date: Mon, 4 Dec 2006 22:23:41 +0100 [thread overview]
Message-ID: <20061204212341.GV8693@postel.suug.ch> (raw)
In-Reply-To: <1165266463.3643.46.camel@localhost>
* jamal <hadi@cyberus.ca> 2006-12-04 16:07
> On Mon, 2006-04-12 at 19:00 +0100, Thomas Graf wrote:
> > * jamal <hadi@cyberus.ca> 2006-12-04 12:48
>
> > > We can resolve that by uping the version for the controller.
> > > User will use that a signal.
> >
> > Good idea, makes me happy :-) please do that in your patch as well.
>
>
> Ok, here she goes...
> If looks good, Dave please apply to net-2.6.20
Looks good.
next prev parent reply other threads:[~2006-12-04 21:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 11:56 [RFC][GENETLINK] move command capabilities to flags jamal
2006-12-04 9:20 ` Thomas Graf
2006-12-04 13:01 ` jamal
2006-12-04 16:31 ` Thomas Graf
2006-12-04 17:48 ` jamal
2006-12-04 18:00 ` Thomas Graf
2006-12-04 21:07 ` jamal
2006-12-04 21:23 ` Thomas Graf [this message]
2006-12-05 3:32 ` David 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=20061204212341.GV8693@postel.suug.ch \
--to=tgraf@suug.ch \
--cc=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=netdev@vger.kernel.org \
/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).