mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: RubenKelevra <rubenkelevra@gmail.com>
Cc: nhorman@tuxdriver.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uapi: net_dropmon: drop unused is_drop_point_hw macro
Date: Wed, 25 Jun 2025 22:50:55 +0000	[thread overview]
Message-ID: <175089185549.646343.1625769414535488237.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250624165711.1188691-1-rubenkelevra@gmail.com>

Hello:

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

On Tue, 24 Jun 2025 18:57:11 +0200 you wrote:
> Commit 4ea7e38696c7 ("dropmon: add ability to detect when hardware
> drops rx packets") introduced is_drop_point_hw, but the symbol was
> never referenced anywhere in the kernel tree and is currently not used
> by dropwatch. I could not find, to the best of my abilities, a current
> out-of-tree user of this macro.
> 
> The definition also contains a syntax error in its for-loop, so any
> project that tried to compile against it would fail. Removing the
> macro therefore eliminates dead code without breaking existing
> users.
> 
> [...]

Here is the summary with links:
  - uapi: net_dropmon: drop unused is_drop_point_hw macro
    https://git.kernel.org/netdev/net-next/c/2855e43c6bb1

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



      reply	other threads:[~2025-06-25 22:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-24 16:57 RubenKelevra
2025-06-25 22:50 ` 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=175089185549.646343.1625769414535488237.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=rubenkelevra@gmail.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®