From: Steffen Klassert <steffen.klassert@secunet.com>
To: David Miller <davem@davemloft.net>
Cc: <subashab@codeaurora.org>, <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] net: xfrm: Change u32 sysctl entries to use proc_douintvec
Date: Thu, 8 Sep 2016 07:51:17 +0200 [thread overview]
Message-ID: <20160908055117.GM31137@gauss.secunet.com> (raw)
In-Reply-To: <20160907.172518.871134561524524971.davem@davemloft.net>
On Wed, Sep 07, 2016 at 05:25:18PM -0700, David Miller wrote:
> From: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
> Date: Tue, 6 Sep 2016 18:09:31 -0600
>
> > proc_dointvec limits the values to INT_MAX in u32 sysctl entries.
> > proc_douintvec allows to write upto UINT_MAX.
> >
> > Signed-off-by: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
>
> I am assuming Steffen will pick this up.
proc_douintvec is not in the ipsec-next tree. The ipsec-next
tree is currently based on net-next from Aug 9. The patch
that introduces proc_douintvec came in on Aug 25.
I can take it after the pull request for ipsec-next, that
I plan to do today. Alternatively, you can take it directly
into net-next. It does not interfere anything that I
have in ipsec-next. In case you want to take it directly:
Acked-by: Steffen Klassert <steffen.klassert@secunet.com>
next prev parent reply other threads:[~2016-09-08 6:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 0:09 [PATCH net-next] net: xfrm: Change u32 sysctl entries to use proc_douintvec Subash Abhinov Kasiviswanathan
2016-09-08 0:25 ` David Miller
2016-09-08 5:51 ` Steffen Klassert [this message]
2016-09-08 6:18 ` 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=20160908055117.GM31137@gauss.secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=subashab@codeaurora.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;
as well as URLs for NNTP newsgroup(s).