netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Moore <paul.moore@hp.com>
To: Thomas Graf <tgraf@suug.ch>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: Generic Netlink Updates
Date: Tue, 14 Nov 2006 12:23:59 -0500	[thread overview]
Message-ID: <4559FBAF.2090004@hp.com> (raw)
In-Reply-To: <20061114114628.033840590@lsx.localdomain>

Thomas Graf wrote:
> Various simplifications to the generic netlink interface partially
> based on suggestions by Paul Moore.

Acked-by: Paul Moore <paul.moore@hp.com>

These changes all look good to me.

-- 
paul moore
linux security @ hp

  parent reply	other threads:[~2006-11-14 17:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-14 11:46 Generic Netlink Updates Thomas Graf
2006-11-14 11:46 ` [PATCH 1/3] [GENL]: Add genlmsg_new() to allocate generic netlink messages Thomas Graf
2006-11-14 11:46 ` [PATCH 2/3] [GENL]: Add genlmsg_reply() to simply unicast replies to requests Thomas Graf
2006-11-14 11:46 ` [PATCH 3/3] [GENL]: Add genlmsg_put_reply() to simplify building reply headers Thomas Graf
2006-11-14 17:23 ` Paul Moore [this message]
2006-11-15  3:46   ` Generic Netlink Updates 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=4559FBAF.2090004@hp.com \
    --to=paul.moore@hp.com \
    --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).