From: David Miller <davem@davemloft.net>
To: avagin@openvz.org
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
xemul@parallels.com, edumazet@google.com,
paulmck@linux.vnet.ibm.com, dhowells@redhat.com
Subject: Re: [PATCH 1/3] net: fix *_DIAG_MAX constants
Date: Thu, 21 Mar 2013 12:37:13 -0400 (EDT) [thread overview]
Message-ID: <20130321.123713.2259863785549784643.davem@davemloft.net> (raw)
In-Reply-To: <1363883628-7249-2-git-send-email-avagin@openvz.org>
From: Andrey Vagin <avagin@openvz.org>
Date: Thu, 21 Mar 2013 20:33:46 +0400
> Follow the common pattern and define *_DIAG_MAX like:
>
> [...]
> __XXX_DIAG_MAX,
> };
>
> Because everyone is used to do:
>
> struct nlattr *attrs[XXX_DIAG_MAX+1];
>
> nla_parse([...], XXX_DIAG_MAX, [...]
>
> Reported-by: Thomas Graf <tgraf@suug.ch>
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: Pavel Emelyanov <xemul@parallels.com>
> Cc: Eric Dumazet <edumazet@google.com>
> Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> Cc: David Howells <dhowells@redhat.com>
> Signed-off-by: Andrey Vagin <avagin@openvz.org>
Applied to 'net' and queued up for -stable.
Thanks.
next prev parent reply other threads:[~2013-03-21 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 16:33 [PATCH 0/3] netlink: implement socket diag for netlink sockets (v2) Andrey Vagin
2013-03-21 16:33 ` [PATCH 1/3] net: fix *_DIAG_MAX constants Andrey Vagin
2013-03-21 16:37 ` David Miller [this message]
2013-03-21 16:33 ` [PATCH 2/3] net: prepare netlink code for netlink diag Andrey Vagin
2013-03-21 16:38 ` David Miller
2013-03-21 16:33 ` [PATCH 3/3] netlink: Diag core and basic socket info dumping (v2) Andrey Vagin
2013-03-21 16:38 ` 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=20130321.123713.2259863785549784643.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=avagin@openvz.org \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=xemul@parallels.com \
/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).