netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
Cc: Thorsten Blum <thorsten.blum@linux.dev>,
	Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
	Xin Long <lucien.xin@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
	<linux-sctp@vger.kernel.org>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next] sctp: Remove commented out code
Date: Wed, 12 Feb 2025 19:57:47 -0800	[thread overview]
Message-ID: <20250212195747.198419a3@kernel.org> (raw)
In-Reply-To: <2c8985fa-4378-4aa2-a56d-c3ca04e8c74c@intel.com>

On Tue, 11 Feb 2025 12:33:57 +0100 Mateusz Polchlopek wrote:
> >> I don't think we want to remove that piece of code, please refer
> >> to the discussion under the link:
> >>
> >> https://lore.kernel.org/netdev/cover.1681917361.git.lucien.xin@gmail.com/  
> > 
> > Hm, the commit message (dbda0fba7a14) says payload was deleted because
> > "the member is not even used anywhere," but it was just commented out.
> > In the cover letter it then explains that "deleted" actually means
> > "commented out."
> > 
> > However, I can't follow the reasoning in the cover letter either:
> > 
> > "Note that instead of completely deleting it, we just leave it as a
> > comment in the struct, signalling to the reader that we do expect
> > such variable parameters over there, as Marcelo suggested."
> > 
> > Where do I find Marcelo's suggestion and the "variable parameters over
> > there?"
> >   
> 
> That's good question, I can't find the Marcelo suggestion that author
> mention. It's hard to find without links to previous series or
> discussion :/
> 
> I guess it should be also commented by maintainers, I see that in the
> Xin's thread Kuba also commented change with commenting out instead
> of removing code. Let's wait

In the linked thread the point was to document what struct will be next
in memory. Here we'd be leaving an array of u8s which isn't very
informative. I see there's precedent in this file, but I vote we just
delete the line.
-- 
pw-bot: cr

  reply	other threads:[~2025-02-13  3:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-11 10:20 [PATCH net-next] sctp: Remove commented out code Thorsten Blum
2025-02-11 10:49 ` Mateusz Polchlopek
2025-02-11 11:17   ` Thorsten Blum
2025-02-11 11:33     ` Mateusz Polchlopek
2025-02-13  3:57       ` Jakub Kicinski [this message]
2025-02-13 10:49         ` Thorsten Blum
2025-02-13 12:05           ` Mateusz Polchlopek
2025-02-13 15:29           ` Jakub Kicinski
2025-02-13 16:50 ` patchwork-bot+netdevbpf

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=20250212195747.198419a3@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sctp@vger.kernel.org \
    --cc=lucien.xin@gmail.com \
    --cc=marcelo.leitner@gmail.com \
    --cc=mateusz.polchlopek@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=thorsten.blum@linux.dev \
    /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).