From: patchwork-bot+netdevbpf@kernel.org
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net-next 0/2] net: Remove the obsolte u64_stats_fetch_*_irq()
Date: Sat, 29 Oct 2022 04:50:19 +0000 [thread overview]
Message-ID: <166701901920.13014.13928137103482337247.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221026132215.696950-1-bigeasy@linutronix.de>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 26 Oct 2022 15:22:13 +0200 you wrote:
> Hi,
>
> This is the removal of u64_stats_fetch_*_irq() users in networking. The
> prerequisites are part of v6.1-rc1. I made two patches, one for net/ and
> the other for drivers/net. Hope that is okay.
> The spi and bpf bits are not part of the series and have been routed
> directly.
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: Remove the obsolte u64_stats_fetch_*_irq() users (drivers).
https://git.kernel.org/netdev/net-next/c/068c38ad88cc
- [net-next,2/2] net: Remove the obsolte u64_stats_fetch_*_irq() users (net).
https://git.kernel.org/netdev/net-next/c/d120d1a63b2c
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:[~2022-10-29 4:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 13:22 [PATCH net-next 0/2] net: Remove the obsolte u64_stats_fetch_*_irq() Sebastian Andrzej Siewior
2022-10-26 13:22 ` [PATCH net-next 1/2] net: Remove the obsolte u64_stats_fetch_*_irq() users (drivers) Sebastian Andrzej Siewior
2022-10-26 13:22 ` [PATCH net-next 2/2] net: Remove the obsolte u64_stats_fetch_*_irq() users (net) Sebastian Andrzej Siewior
2022-10-29 4:50 ` 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=166701901920.13014.13928137103482337247.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--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.