From: Thomas Graf <tgraf@suug.ch>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org
Subject: [PATCH 0/8] [RESEND] netlink error magngement + others
Date: Thu, 22 Mar 2007 23:18:04 +0100 [thread overview]
Message-ID: <20070322221804.000124130@lsx.localdomain> (raw)
Dave,
I've rediffed all patches and combined the two patchsets into
one. Patrick has already queued the NLM_F_REQUEST change for
nfnetlink.
[PATCH 0/5] [PATCHSET] Netlink Patches
Converts westwood and vegas netlink code to use the typesafe
interface, removes an unused varaible, and move some netlink
queue management code into the generic layer.
[PATCH 0/3] [PATCHSET] netlink error management
This series of patches simplifies the error management and
signalization of dump starts of netlink_run_queue() message
handlers. It touches a fair bit of nfnetlink code as the
error pointer has been passed on to subsystems.
next reply other threads:[~2007-03-22 22:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 22:18 Thomas Graf [this message]
2007-03-22 22:18 ` [PATCH 1/8] [TCP] vegas: Use type safe netlink interface Thomas Graf
2007-03-22 22:18 ` [PATCH 2/8] [TCP] westwood: " Thomas Graf
2007-03-22 22:18 ` [PATCH 3/8] [NETLINK]: Remove unused groups variable Thomas Graf
2007-03-22 22:18 ` [PATCH 4/8] [NETLINK]: Ignore !NLM_F_REQUEST messages directly in netlink_run_queue() Thomas Graf
2007-03-22 22:18 ` [PATCH 5/8] [NETLINK]: Ignore control " Thomas Graf
2007-03-22 22:18 ` [PATCH 6/8] [NETLINK]: Remove error pointer from netlink message handler Thomas Graf
2007-03-22 22:18 ` [PATCH 7/8] [IPv4] diag: Use netlink_run_queue() to process the receive queue Thomas Graf
2007-03-22 22:18 ` [PATCH 8/8] [NETLINK]: Directly return -EINTR from netlink_dump_start() Thomas Graf
2007-03-23 6:31 ` [PATCH 0/8] [RESEND] netlink error magngement + others 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=20070322221804.000124130@lsx.localdomain \
--to=tgraf@suug.ch \
--cc=davem@davemloft.net \
--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