linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Joel Granados <joel.granados@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
	 Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
	Muchun Song <muchun.song@linux.dev>,
	 Oscar Salvador <osalvador@suse.de>,
	David Hildenbrand <david@kernel.org>,
	 Petr Mladek <pmladek@suse.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	 John Ogness <john.ogness@linutronix.de>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	 "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	 Jakub Kicinski <kuba@kernel.org>,
	Simon Horman <horms@kernel.org>,
	linux-fsdevel@vger.kernel.org,  linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, linux-hams@vger.kernel.org,
	 netdev@vger.kernel.org
Subject: Re: [PATCH v2] sysctl: Remove unused ctl_table forward declarations
Date: Fri, 19 Dec 2025 12:03:26 +0100	[thread overview]
Message-ID: <warv3zwcd4o3rbowav7bhziz6w6lzsuqeeiq4ekpqyj76jwuxf@jmodw3stxult> (raw)
In-Reply-To: <1491a7c7-3ff8-4aea-a6ee-4950f65c756f@redhat.com>

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

On Fri, Dec 19, 2025 at 10:28:31AM +0100, Paolo Abeni wrote:
> On 12/17/25 1:16 PM, Joel Granados wrote:
> > Remove superfluous forward declarations of ctl_table from header files
> > where they are no longer needed. These declarations were left behind
> > after sysctl code refactoring and cleanup.
> > 
> > Reviewed-by: Jan Kara <jack@suse.cz>
> > Acked-by: Muchun Song <muchun.song@linux.dev>
> > Reviewed-by: Petr Mladek <pmladek@suse.com>
> > Signed-off-by: Joel Granados <joel.granados@kernel.org>
> > ---
> > Apologies for such a big To: list. My idea is for this to go into
> > mainline through sysctl; get back to me if you prefer otherwise. On the
> > off chance that this has a V3, let me know if you want to be removed
> > from the To and I'll make that happen
> 
> For the net bits:
> 
> Acked-by: Paolo Abeni <pabeni@redhat.com>
> 
> I'm ok with merging this via the sysctl tree, given that we don't see
> much action happening in the ax25 header (and very low chances of
> conflicts). But I would be also ok if you would split this into multiple
> patches, one for each affected subsystem.
I'll separate it, if I send a V3

Thx for the feedback.

-- 

Joel Granados

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

      reply	other threads:[~2025-12-19 11:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-17 12:16 Joel Granados
2025-12-19  9:28 ` Paolo Abeni
2025-12-19 11:03   ` 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=warv3zwcd4o3rbowav7bhziz6w6lzsuqeeiq4ekpqyj76jwuxf@jmodw3stxult \
    --to=joel.granados@kernel.org \
    --cc=brauner@kernel.org \
    --cc=davem@davemloft.net \
    --cc=david@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jack@suse.cz \
    --cc=john.ogness@linutronix.de \
    --cc=kuba@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-hams@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=muchun.song@linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=osalvador@suse.de \
    --cc=pabeni@redhat.com \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.org \
    --cc=viro@zeniv.linux.org.uk \
    /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