Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Slawomir Stepien <sst@poczta.fm>
Cc: kuba@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net,
	edumazet@google.com, pabeni@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	syzbot@lists.linux.dev,
	syzbot+3147c5de186107ffc7a1@syzkaller.appspotmail.com
Subject: Re: [PATCH v2] netdevsim: drop the ability to change max_vfs via debugfs
Date: Fri, 14 Aug 2026 03:24:22 +0000	[thread overview]
Message-ID: <178667786239.3150297.10278646018244471870.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260810085717.570382-1-sst@poczta.fm>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 10 Aug 2026 10:57:17 +0200 you wrote:
> This debugfs file isn't used by kernel's selftests, so drop it.
> 
> Reported-by: syzbot+3147c5de186107ffc7a1@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=3147c5de186107ffc7a1
> Suggested-by: Jakub Kicinski <kuba@kernel.org>
> Signed-off-by: Slawomir Stepien <sst@poczta.fm>
> 
> [...]

Here is the summary with links:
  - [v2] netdevsim: drop the ability to change max_vfs via debugfs
    https://git.kernel.org/netdev/net-next/c/b3217bdb0091

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2026-08-14  3:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-10  8:57 [PATCH v2] netdevsim: drop the ability to change max_vfs via debugfs Slawomir Stepien
2026-08-14  3:24 ` patchwork-bot+netdevbpf [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=178667786239.3150297.10278646018244471870.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sst@poczta.fm \
    --cc=syzbot+3147c5de186107ffc7a1@syzkaller.appspotmail.com \
    --cc=syzbot@lists.linux.dev \
    --cc=syzkaller-bugs@googlegroups.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