netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, claudiu.manoil@nxp.com,
	xiaoliang.yang_1@nxp.com
Subject: Re: [PATCH net-next 0/6] ENETC MAC Merge cleanup
Date: Mon, 23 Jan 2023 13:20:16 +0000	[thread overview]
Message-ID: <167448001662.10090.11580039630545061099.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230119160431.295833-1-vladimir.oltean@nxp.com>

Hello:

This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Thu, 19 Jan 2023 18:04:25 +0200 you wrote:
> This is a preparatory patch set for MAC Merge layer support in enetc via
> ethtool. It does the following:
> 
> - consolidates a software lockstep register write procedure for the pMAC
> - detects per-port frame preemption capability and only writes pMAC
>   registers if a pMAC exists
> - stops enabling the pMAC by default
> 
> [...]

Here is the summary with links:
  - [net-next,1/6] net: enetc: build common object files into a separate module
    https://git.kernel.org/netdev/net-next/c/e3972399bb57
  - [net-next,2/6] net: enetc: detect frame preemption hardware capability
    https://git.kernel.org/netdev/net-next/c/94557a9a73b4
  - [net-next,3/6] net: enetc: add definition for offset between eMAC and pMAC regs
    https://git.kernel.org/netdev/net-next/c/9c949e0b2f9c
  - [net-next,4/6] net: enetc: stop configuring pMAC in lockstep with eMAC
    https://git.kernel.org/netdev/net-next/c/219355f1b093
  - [net-next,5/6] net: enetc: implement software lockstep for port MAC registers
    https://git.kernel.org/netdev/net-next/c/12717decb570
  - [net-next,6/6] net: enetc: stop auto-configuring the port pMAC
    https://git.kernel.org/netdev/net-next/c/086cc0803550

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



      parent reply	other threads:[~2023-01-23 13:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 16:04 [PATCH net-next 0/6] ENETC MAC Merge cleanup Vladimir Oltean
2023-01-19 16:04 ` [PATCH net-next 1/6] net: enetc: build common object files into a separate module Vladimir Oltean
2023-01-19 16:04 ` [PATCH net-next 2/6] net: enetc: detect frame preemption hardware capability Vladimir Oltean
2023-01-19 16:04 ` [PATCH net-next 3/6] net: enetc: add definition for offset between eMAC and pMAC regs Vladimir Oltean
2023-01-22 16:29   ` Simon Horman
2023-01-23 11:24     ` Vladimir Oltean
2023-01-23 12:44       ` Simon Horman
2023-01-19 16:04 ` [PATCH net-next 4/6] net: enetc: stop configuring pMAC in lockstep with eMAC Vladimir Oltean
2023-01-19 16:04 ` [PATCH net-next 5/6] net: enetc: implement software lockstep for port MAC registers Vladimir Oltean
2023-01-19 16:04 ` [PATCH net-next 6/6] net: enetc: stop auto-configuring the port pMAC Vladimir Oltean
2023-01-23 13:20 ` 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=167448001662.10090.11580039630545061099.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=claudiu.manoil@nxp.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=vladimir.oltean@nxp.com \
    --cc=xiaoliang.yang_1@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).