netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joel Granados <j.granados@samsung.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
	Iurii Zaikin <yzaikin@google.com>, <willy@infradead.org>,
	<josh@joshtriplett.org>, <linux-kernel@vger.kernel.org>,
	<linux-fsdevel@vger.kernel.org>, <netdev@vger.kernel.org>
Subject: Re: [PATCH 00/14] sysctl: Add a size argument to register functions in sysctl
Date: Fri, 28 Jul 2023 09:04:56 +0200	[thread overview]
Message-ID: <20230728070456.zkzuh5caofkvvupj@localhost> (raw)
In-Reply-To: <ZMKPzzkVy45lSCJ7@bombadil.infradead.org>

[-- Attachment #1: Type: text/plain, Size: 998 bytes --]

On Thu, Jul 27, 2023 at 08:39:59AM -0700, Luis Chamberlain wrote:
> On Thu, Jul 27, 2023 at 01:43:18PM +0200, Joel Granados wrote:
> > On Wed, Jul 26, 2023 at 11:15:40AM -0700, Luis Chamberlain wrote:
> > > On Wed, Jul 26, 2023 at 04:06:20PM +0200, Joel Granados wrote:
> > > > What?
> > > > These commits set things up so we can start removing the sentinel elements.
> > > 
> > > Yes but the why must explained right away.
> > My intention of putting the "what" first was to explain the chunking and
> 
> It may help also just to clarify:
> 
>    sentinel, the extra empty struct ctl_table at the end of each
>    sysctl array.
This clarification is already there: "... sentinel element (the extra
empty element in the ctl_table arrays ...".

> 
> > Thx for this.
> > This is a more clear wording for the "Why". Do you mind if I copy/paste
> > it (with some changes to make it flow) into my next cover letter?
> 
> I don't mind at all.
> 
>   Luis

-- 

Joel Granados

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

      reply	other threads:[~2023-07-28  7:05 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20230726140656eucas1p26cd9da21663d25b51dda75258aaa3b55@eucas1p2.samsung.com>
     [not found] ` <20230726140635.2059334-1-j.granados@samsung.com>
2023-07-26 14:06   ` [PATCH 05/14] sysctl: Add a size arg to __register_sysctl_table Joel Granados
2023-07-28 10:51     ` Simon Horman
2023-07-28 16:08       ` Joel Granados
2023-07-26 14:06   ` [PATCH 06/14] sysctl: Add size to register_sysctl Joel Granados
2023-07-26 17:58     ` Luis Chamberlain
2023-07-27 12:22       ` Joel Granados
2023-07-27 15:42         ` Luis Chamberlain
2023-07-28  7:41           ` Joel Granados
2023-07-26 14:06   ` [PATCH 08/14] sysctl: Add size to register_net_sysctl function Joel Granados
2023-07-26 14:06   ` [PATCH 09/14] ax.25: Update to register_net_sysctl_sz Joel Granados
2023-07-26 18:00     ` Luis Chamberlain
2023-07-27 12:31       ` Joel Granados
2023-07-27 15:44         ` Luis Chamberlain
2023-07-28  7:35           ` Joel Granados
2023-07-28 18:16             ` Luis Chamberlain
2023-07-31  7:09               ` Joel Granados
2023-07-27 15:38       ` Joel Granados
2023-07-27 15:50         ` Luis Chamberlain
2023-07-26 14:06   ` [PATCH 10/14] netfilter: " Joel Granados
2023-07-26 18:01     ` Luis Chamberlain
2023-07-26 14:06   ` [PATCH 11/14] networking: " Joel Granados
2023-07-26 18:05     ` Luis Chamberlain
2023-07-27  0:33       ` David Ahern
2023-07-27 12:33       ` Joel Granados
2023-07-28  7:08       ` Joel Granados
2023-07-26 14:06   ` [PATCH 12/14] vrf: " Joel Granados
2023-07-26 14:06   ` [PATCH 13/14] sysctl: SIZE_MAX->ARRAY_SIZE in register_net_sysctl Joel Granados
2023-07-26 18:15   ` [PATCH 00/14] sysctl: Add a size argument to register functions in sysctl Luis Chamberlain
2023-07-27 11:43     ` Joel Granados
2023-07-27 15:39       ` Luis Chamberlain
2023-07-28  7:04         ` Joel Granados [this message]

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=20230728070456.zkzuh5caofkvvupj@localhost \
    --to=j.granados@samsung.com \
    --cc=josh@joshtriplett.org \
    --cc=keescook@chromium.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=willy@infradead.org \
    --cc=yzaikin@google.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).