From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
michael@walle.cc, claudiu.manoil@nxp.com,
alexandru.marginean@nxp.com
Subject: Re: [PATCH net] net: enetc: initialize the RFS and RSS memories
Date: Fri, 05 Feb 2021 04:40:07 +0000 [thread overview]
Message-ID: <161250000742.27819.3538406306953054880.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210204134511.2640309-1-vladimir.oltean@nxp.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Thu, 4 Feb 2021 15:45:11 +0200 you wrote:
> Michael tried to enable Advanced Error Reporting through the ENETC's
> Root Complex Event Collector, and the system started spitting out single
> bit correctable ECC errors coming from the ENETC interfaces:
>
> pcieport 0000:00:1f.0: AER: Multiple Corrected error received: 0000:00:00.0
> fsl_enetc 0000:00:00.0: PCIe Bus Error: severity=Corrected, type=Transaction Layer, (Receiver ID)
> fsl_enetc 0000:00:00.0: device [1957:e100] error status/mask=00004000/00000000
> fsl_enetc 0000:00:00.0: [14] CorrIntErr
> fsl_enetc 0000:00:00.1: PCIe Bus Error: severity=Corrected, type=Transaction Layer, (Receiver ID)
> fsl_enetc 0000:00:00.1: device [1957:e100] error status/mask=00004000/00000000
> fsl_enetc 0000:00:00.1: [14] CorrIntErr
>
> [...]
Here is the summary with links:
- [net] net: enetc: initialize the RFS and RSS memories
https://git.kernel.org/netdev/net/c/07bf34a50e32
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-02-05 4:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 13:45 [PATCH net] net: enetc: initialize the RFS and RSS memories Vladimir Oltean
2021-02-04 13:51 ` Michael Walle
2021-02-05 1:13 ` Jesse Brandeburg
2021-02-05 4:40 ` 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=161250000742.27819.3538406306953054880.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandru.marginean@nxp.com \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
--cc=vladimir.oltean@nxp.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).