From: Patrick McHardy <kaber@trash.net>
To: Thomas Graf <tgraf@suug.ch>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [NETFILTER] nfnetlink: netlink_run_queue() already checks for NLM_F_REQUEST
Date: Wed, 21 Mar 2007 13:37:23 +0100 [thread overview]
Message-ID: <46012703.8060205@trash.net> (raw)
In-Reply-To: <20070321123304.GV521@postel.suug.ch>
Thomas Graf wrote:
> Patrick has made use of netlink_run_queue() in nfnetlink while my patches
> have been waiting for net-2.6.22 to open. So this check for NLM_F_REQUEST
> can go as well.
Looks good, thanks. I've added it to my queue.
next prev parent reply other threads:[~2007-03-21 12:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 0:18 [PATCH 0/5] [PATCHSET] Netlink Patches Thomas Graf
2007-03-21 0:18 ` [PATCH 1/5] [TCP] vegas: Use type safe netlink interface Thomas Graf
2007-03-21 0:18 ` [PATCH 2/5] [TCP] westwood: " Thomas Graf
2007-03-21 0:18 ` [PATCH 3/5] [NETLINK]: Remove unused groups variable Thomas Graf
2007-03-21 0:18 ` [PATCH 4/5] [NETLINK]: Ignore !NLM_F_REQUEST messages directly in netlink_run_queue() Thomas Graf
2007-03-21 12:33 ` [NETFILTER] nfnetlink: netlink_run_queue() already checks for NLM_F_REQUEST Thomas Graf
2007-03-21 12:37 ` Patrick McHardy [this message]
2007-03-21 0:18 ` [PATCH 5/5] [NETLINK]: Ignore control messages directly in netlink_run_queue() Thomas Graf
2007-03-21 4:44 ` Patrick McHardy
2007-03-21 11:45 ` Thomas Graf
2007-03-21 11:59 ` Thomas Graf
2007-03-21 12:06 ` Patrick McHardy
2007-03-21 12:21 ` Patrick McHardy
2007-03-21 12:25 ` Thomas Graf
2007-03-21 12:25 ` Thomas Graf
-- strict thread matches above, loose matches on Subject: below --
2007-03-23 14:04 [NETFILTER 00/12]: Netfilter update part II Patrick McHardy
2007-03-23 14:05 ` [NETFILTER] nfnetlink: netlink_run_queue() already checks for NLM_F_REQUEST Patrick McHardy
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=46012703.8060205@trash.net \
--to=kaber@trash.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.