netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Moon Yeounsu <yyyynoom@gmail.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3] net: dlink: enable RMON MMIO access on supported devices
Date: Wed, 11 Jun 2025 01:00:35 +0000	[thread overview]
Message-ID: <174960363599.2754897.17312304165286699785.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250610000130.49065-2-yyyynoom@gmail.com>

Hello:

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

On Tue, 10 Jun 2025 09:01:30 +0900 you wrote:
> Enable memory-mapped I/O access to RMON statistics registers for devices
> known to work correctly. Currently, only the D-Link DGE-550T (`0x4000`)
> with PCI revision A3 (`0x0c`) is allowed.
> 
> To avoid issues on other hardware, a runtime check was added to restrict
> MMIO usage. The `MEM_MAPPING` macro was removed in favor of runtime
> detection.
> 
> [...]

Here is the summary with links:
  - [net-next,v3] net: dlink: enable RMON MMIO access on supported devices
    https://git.kernel.org/netdev/net-next/c/7fc18f947625

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-11  1:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10  0:01 [PATCH net-next v3] net: dlink: enable RMON MMIO access on supported devices Moon Yeounsu
2025-06-11  1:00 ` 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=174960363599.2754897.17312304165286699785.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=yyyynoom@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;
as well as URLs for NNTP newsgroup(s).