netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Benc <jbenc@redhat.com>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>
Cc: netdev@vger.kernel.org, Thomas Graf <tgraf@suug.ch>
Subject: Re: [RFC PATCH net-next 0/9] netlink: strict attribute checking option
Date: Fri, 16 Oct 2015 09:49:51 +0200	[thread overview]
Message-ID: <20151016094951.11146959@griffin> (raw)
In-Reply-To: <87r3kv3hwv.fsf@stressinduktion.org>

On Fri, 16 Oct 2015 00:07:12 +0200, Hannes Frederic Sowa wrote:
> Do you plan to update rfc3549, too? :}

No.

While I think we need to have a detailed documentation on netlink,
I believe it should reside in Documentation/ inside the kernel tree to
be easily updated, not in an outside document collection with much more
heavyweight processes around getting something updated.

I would offer taking the RFC 3549 into the kernel tree and extending it
but my understanding of the license is that I'm not allowed to do that
(as I would modify the "document itself").

 Jiri

-- 
Jiri Benc

  reply	other threads:[~2015-10-16  7:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15 16:39 [RFC PATCH net-next 0/9] netlink: strict attribute checking option Jiri Benc
2015-10-15 16:39 ` [RFC PATCH net-next 1/9] netlink: add NLM_F_STRICT for strict attribute checking Jiri Benc
2015-10-15 16:39 ` [RFC PATCH net-next 2/9] netlink: remove unnecesary goto's Jiri Benc
2015-10-15 16:39 ` [RFC PATCH net-next 3/9] netlink: strict attribute parsing Jiri Benc
2015-10-15 16:39 ` [RFC PATCH net-next 4/9] netlink: strict attribute validation Jiri Benc
2015-10-15 16:39 ` [RFC PATCH net-next 5/9] rtnetlink: support strict attribute checking Jiri Benc
2015-10-15 16:39 ` [RFC PATCH net-next 6/9] rtnetlink: add strict parameter to validate callbacks Jiri Benc
2015-10-15 16:39 ` [RFC PATCH net-next 7/9] rtnetlink: add strict parameter to validate_link_af Jiri Benc
2015-10-15 16:39 ` [RFC PATCH net-next 8/9] rtnetlink: support strict checking for newlink, setlink and dellink Jiri Benc
2015-10-15 16:39 ` [RFC PATCH net-next 9/9] veth: validate nested attributes Jiri Benc
2015-10-15 22:07 ` [RFC PATCH net-next 0/9] netlink: strict attribute checking option Hannes Frederic Sowa
2015-10-16  7:49   ` Jiri Benc [this message]
2015-10-16  8:08     ` David Miller
2015-10-16  8:08       ` Jiri Benc
2015-10-16  9:40         ` Hannes Frederic Sowa
2015-10-16 10:00           ` Jiri Benc
2015-10-16  6:50 ` David Miller
2015-10-16  7:39   ` Jiri Benc
2015-10-16  8:06     ` David Miller
2015-10-16  8:02       ` Jiri Benc
2015-10-16  8:09         ` Thomas Graf
2015-10-16 15:57         ` David Ahern
2015-10-19  2:29           ` 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=20151016094951.11146959@griffin \
    --to=jbenc@redhat.com \
    --cc=hannes@stressinduktion.org \
    --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).