public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux@ew.tq-group.com
Subject: Re: [PATCH net-next v2 1/2] net: phy: marvell: constify marvell_hw_stats
Date: Tue, 07 May 2024 22:30:29 +0000	[thread overview]
Message-ID: <171512102970.11788.7481249283521486733.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <24d7a2f39e0c4c94466e8ad43228fdd798053f3a.1714643285.git.matthias.schiffer@ew.tq-group.com>

Hello:

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

On Thu,  2 May 2024 13:13:00 +0200 you wrote:
> The list of stat registers is read-only, so we can declare it as const.
> 
> Signed-off-by: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
> ---
> 
> v2: New patch
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/2] net: phy: marvell: constify marvell_hw_stats
    https://git.kernel.org/netdev/net-next/c/71dd027ab453
  - [net-next,v2,2/2] net: phy: marvell: add support for MV88E6250 family internal PHYs
    https://git.kernel.org/netdev/net-next/c/ecc2ae6176a9

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



      parent reply	other threads:[~2024-05-07 22:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-02 11:13 [PATCH net-next v2 1/2] net: phy: marvell: constify marvell_hw_stats Matthias Schiffer
2024-05-02 11:13 ` [PATCH net-next v2 2/2] net: phy: marvell: add support for MV88E6250 family internal PHYs Matthias Schiffer
2024-05-07 12:18   ` Andrew Lunn
2024-05-07 12:14 ` [PATCH net-next v2 1/2] net: phy: marvell: constify marvell_hw_stats Andrew Lunn
2024-05-07 22:30 ` 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=171512102970.11788.7481249283521486733.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=linux@ew.tq-group.com \
    --cc=matthias.schiffer@ew.tq-group.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox