mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jacob Keller <jacob.e.keller@intel.com>
To: Jakub Kicinski <kuba@kernel.org>, Artem Lytkin <iprintercanon@gmail.com>
Cc: <netdev@vger.kernel.org>, <davem@davemloft.net>,
	<edumazet@google.com>, <pabeni@redhat.com>, <horms@kernel.org>,
	<donald.hunter@gmail.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v2] rtnetlink: cap IFLA_VFINFO_LIST at a documented number of VFs
Date: Thu, 30 Jul 2026 16:14:46 -0700	[thread overview]
Message-ID: <67e5ddca-43a0-428d-9dae-eddff828a26c@intel.com> (raw)
In-Reply-To: <20260730140931.14d5bf4b@kernel.org>

On 7/30/2026 2:09 PM, Jakub Kicinski wrote:
> And FWIW (sorry, Im going to reply here to avoid splintering) I maintain
> that net-next is better :) We are capping, who knows is someone
> complains. So I _don't_ want this in LTS.
> 

Fair enough, no objections here. I'd appreciate something in the commit
message mentioning the commit this originated in, since that may still
be helpful to future readers for context, but I won't hold an objection
regardless of what ends up in v3.

Thanks,
Jake

  reply	other threads:[~2026-07-30 23:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-25 13:22 [PATCH net] rtnetlink: truncate IFLA_VFINFO_LIST instead of overflowing its length Artem Lytkin
2026-07-30  1:55 ` Jakub Kicinski
2026-07-30  9:07   ` [PATCH net-next v2] rtnetlink: cap IFLA_VFINFO_LIST at a documented number of VFs Artem Lytkin
2026-07-30 21:09     ` Jakub Kicinski
2026-07-30 23:14       ` Jacob Keller [this message]
2026-07-30  9:17   ` [PATCH net] rtnetlink: truncate IFLA_VFINFO_LIST instead of overflowing its length Jacob Keller
2026-07-30 17:12     ` Artem Lytkin

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=67e5ddca-43a0-428d-9dae-eddff828a26c@intel.com \
    --to=jacob.e.keller@intel.com \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=iprintercanon@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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
all inboxes | Powered by JetHome®