From: patchwork-bot+netdevbpf@kernel.org
To: Jesper Nilsson <jesper.nilsson@axis.com>
Cc: alexandre.torgue@foss.st.com, joabreu@synopsys.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, mcoquelin.stm32@gmail.com,
netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@axis.com,
fancer.lancer@gmail.com
Subject: Re: [PATCH net-next v3] net: stmmac: mmc_core: Drop interrupt registers from stats
Date: Tue, 27 Feb 2024 10:40:30 +0000 [thread overview]
Message-ID: <170903043028.17630.12024992708013538596.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240223-stmmac_stats-v3-1-5d483c2a071a@axis.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 23 Feb 2024 21:37:01 +0100 you wrote:
> The MMC IPC interrupt status and interrupt mask registers are
> of little use as Ethernet statistics, but incrementing counters
> based on the current interrupt and interrupt mask registers
> makes them actively misleading.
>
> For example, if the interrupt mask is set to 0x08420842,
> the current code will increment by that amount each iteration,
> leading to the following sequence of nonsense:
>
> [...]
Here is the summary with links:
- [net-next,v3] net: stmmac: mmc_core: Drop interrupt registers from stats
https://git.kernel.org/netdev/net-next/c/d0dc1e42109d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Jesper Nilsson <jesper.nilsson@axis.com>
Cc: alexandre.torgue@foss.st.com, joabreu@synopsys.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, mcoquelin.stm32@gmail.com,
netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@axis.com,
fancer.lancer@gmail.com
Subject: Re: [PATCH net-next v3] net: stmmac: mmc_core: Drop interrupt registers from stats
Date: Tue, 27 Feb 2024 10:40:30 +0000 [thread overview]
Message-ID: <170903043028.17630.12024992708013538596.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240223-stmmac_stats-v3-1-5d483c2a071a@axis.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 23 Feb 2024 21:37:01 +0100 you wrote:
> The MMC IPC interrupt status and interrupt mask registers are
> of little use as Ethernet statistics, but incrementing counters
> based on the current interrupt and interrupt mask registers
> makes them actively misleading.
>
> For example, if the interrupt mask is set to 0x08420842,
> the current code will increment by that amount each iteration,
> leading to the following sequence of nonsense:
>
> [...]
Here is the summary with links:
- [net-next,v3] net: stmmac: mmc_core: Drop interrupt registers from stats
https://git.kernel.org/netdev/net-next/c/d0dc1e42109d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-02-27 10:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 20:37 [PATCH net-next v3] net: stmmac: mmc_core: Drop interrupt registers from stats Jesper Nilsson
2024-02-23 20:37 ` Jesper Nilsson
2024-02-26 9:22 ` Jiri Pirko
2024-02-26 9:22 ` Jiri Pirko
2024-02-27 10:40 ` patchwork-bot+netdevbpf [this message]
2024-02-27 10:40 ` 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=170903043028.17630.12024992708013538596.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fancer.lancer@gmail.com \
--cc=jesper.nilsson@axis.com \
--cc=joabreu@synopsys.com \
--cc=kernel@axis.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.