From: patchwork-bot+netdevbpf@kernel.org
To: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: netdev@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, nathan@kernel.org, ndesaulniers@google.com,
morbo@google.com, justinstitt@google.com,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
vladimir.oltean@nxp.com
Subject: Re: [PATCH net-next v2 0/2] net: systemport: Minor IO macros changes
Date: Mon, 28 Oct 2024 23:00:42 +0000 [thread overview]
Message-ID: <173015644200.206744.11510242764690126577.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241021174935.57658-1-florian.fainelli@broadcom.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 21 Oct 2024 10:49:33 -0700 you wrote:
> This patch series addresses the warning initially reported by Vladimir
> here:
>
> https://lore.kernel.org/all/20241014150139.927423-1-vladimir.oltean@nxp.com/
>
> and follows on with proceeding with his suggestion the IO macros to the
> header file.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net: systemport: Remove unused txchk accessors
https://git.kernel.org/netdev/net-next/c/890bde75a236
- [net-next,v2,2/2] net: systemport: Move IO macros to header file
https://git.kernel.org/netdev/net-next/c/e69fbd287d5a
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:[~2024-10-28 23:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 17:49 [PATCH net-next v2 0/2] net: systemport: Minor IO macros changes Florian Fainelli
2024-10-21 17:49 ` [PATCH net-next v2 1/2] net: systemport: Remove unused txchk accessors Florian Fainelli
2024-10-23 18:42 ` Simon Horman
2024-10-21 17:49 ` [PATCH net-next v2 2/2] net: systemport: Move IO macros to header file Florian Fainelli
2024-10-23 18:42 ` Simon Horman
2024-10-28 23: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=173015644200.206744.11510242764690126577.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=justinstitt@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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 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.