From: patchwork-bot+netdevbpf@kernel.org
To: Rosen Penev <rosenp@gmail.com>
Cc: netdev@vger.kernel.org, shayagr@amazon.com, akiyano@amazon.com,
darinzon@amazon.com, ndagan@amazon.com, saeedb@amazon.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, shenjian15@huawei.com,
salil.mehta@huawei.com, shaojijie@huawei.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] net: ena: two cleanups
Date: Tue, 05 Nov 2024 02:30:45 +0000 [thread overview]
Message-ID: <173077384548.92170.17025072705900233883.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241101214828.289752-1-rosenp@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 1 Nov 2024 14:48:26 -0700 you wrote:
> Simplify some code.
>
> Rosen Penev (2):
> net: ena: remove devm from ethtool
> net: ena: simplify some pointer addition
>
> drivers/net/ethernet/amazon/ena/ena_ethtool.c | 31 ++++++++-----------
> 1 file changed, 13 insertions(+), 18 deletions(-)
Here is the summary with links:
- [net-next,1/2] net: ena: remove devm from ethtool
https://git.kernel.org/netdev/net-next/c/d2068805f688
- [net-next,2/2] net: ena: simplify some pointer addition
(no matching commit)
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-11-05 2:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 21:48 Rosen Penev
2024-11-01 21:48 ` [PATCH net-next 1/2] net: ena: remove devm from ethtool Rosen Penev
2024-11-04 13:35 ` Shay Agroskin
2024-11-01 21:48 ` [PATCH net-next 2/2] net: ena: simplify some pointer addition Rosen Penev
2024-11-04 13:36 ` Shay Agroskin
2024-11-05 2: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=173077384548.92170.17025072705900233883.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=akiyano@amazon.com \
--cc=andrew+netdev@lunn.ch \
--cc=darinzon@amazon.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ndagan@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rosenp@gmail.com \
--cc=saeedb@amazon.com \
--cc=salil.mehta@huawei.com \
--cc=shaojijie@huawei.com \
--cc=shayagr@amazon.com \
--cc=shenjian15@huawei.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
Powered by JetHome