From: patchwork-bot+netdevbpf@kernel.org
To: Shay Agroskin <shayagr@amazon.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
dwmw@amazon.com, zorik@amazon.com, matua@amazon.com,
saeedb@amazon.com, msw@amazon.com, aliguori@amazon.com,
nafea@amazon.com, netanel@amazon.com, alisaidi@amazon.com,
benh@amazon.com, akiyano@amazon.com, ndagan@amazon.com
Subject: Re: [Patch v1 net-next 00/10] Use build_skb and reorganize some code in ENA
Date: Tue, 08 Jun 2021 21:50:09 +0000 [thread overview]
Message-ID: <162318900943.8715.3406966963040622626.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210608160118.3767932-1-shayagr@amazon.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Tue, 8 Jun 2021 19:01:08 +0300 you wrote:
> Hi all,
> this patchset introduces several changes:
>
> - Use build_skb() on RX side.
> This allows to ensure that the headers are in the linear part
>
> - Batch some code into functions and remove some of the code to make it more
> readable and less error prone
>
> [...]
Here is the summary with links:
- [v1,net-next,01/10] net: ena: optimize data access in fast-path code
https://git.kernel.org/netdev/net-next/c/e4ac382ebfb4
- [v1,net-next,02/10] net: ena: Remove unused code
https://git.kernel.org/netdev/net-next/c/9912c72edd8c
- [v1,net-next,03/10] net: ena: Improve error logging in driver
https://git.kernel.org/netdev/net-next/c/091d0e85a0d4
- [v1,net-next,04/10] net: ena: use build_skb() in RX path
https://git.kernel.org/netdev/net-next/c/9e5269a915a8
- [v1,net-next,05/10] net: ena: add jiffies of last napi call to stats
https://git.kernel.org/netdev/net-next/c/0ee251cd9a63
- [v1,net-next,06/10] net: ena: Remove module param and change message severity
https://git.kernel.org/netdev/net-next/c/15efff76491e
- [v1,net-next,07/10] net: ena: fix RST format in ENA documentation file
https://git.kernel.org/netdev/net-next/c/511c537bb564
- [v1,net-next,08/10] net: ena: aggregate doorbell common operations into a function
https://git.kernel.org/netdev/net-next/c/9e8afb059611
- [v1,net-next,09/10] net: ena: Use dev_alloc() in RX buffer allocation
https://git.kernel.org/netdev/net-next/c/947c54c395cb
- [v1,net-next,10/10] net: ena: re-organize code to improve readability
https://git.kernel.org/netdev/net-next/c/a01f2cd0ccf4
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:[~2021-06-08 21:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 16:01 [Patch v1 net-next 00/10] Use build_skb and reorganize some code in ENA Shay Agroskin
2021-06-08 16:01 ` [Patch v1 net-next 01/10] net: ena: optimize data access in fast-path code Shay Agroskin
2021-06-08 16:01 ` [Patch v1 net-next 02/10] net: ena: Remove unused code Shay Agroskin
2021-06-08 16:01 ` [Patch v1 net-next 03/10] net: ena: Improve error logging in driver Shay Agroskin
2021-06-08 16:01 ` [Patch v1 net-next 04/10] net: ena: use build_skb() in RX path Shay Agroskin
2021-06-08 16:01 ` [Patch v1 net-next 05/10] net: ena: add jiffies of last napi call to stats Shay Agroskin
2021-06-08 16:01 ` [Patch v1 net-next 06/10] net: ena: Remove module param and change message severity Shay Agroskin
2021-06-08 16:01 ` [Patch v1 net-next 07/10] net: ena: fix RST format in ENA documentation file Shay Agroskin
2021-06-08 16:01 ` [Patch v1 net-next 08/10] net: ena: aggregate doorbell common operations into a function Shay Agroskin
2021-06-08 16:01 ` [Patch v1 net-next 09/10] net: ena: Use dev_alloc() in RX buffer allocation Shay Agroskin
2021-06-08 19:25 ` kernel test robot
2021-06-08 19:25 ` kernel test robot
2021-06-08 16:01 ` [Patch v1 net-next 10/10] net: ena: re-organize code to improve readability Shay Agroskin
2021-06-08 21: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=162318900943.8715.3406966963040622626.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=akiyano@amazon.com \
--cc=aliguori@amazon.com \
--cc=alisaidi@amazon.com \
--cc=benh@amazon.com \
--cc=davem@davemloft.net \
--cc=dwmw@amazon.com \
--cc=kuba@kernel.org \
--cc=matua@amazon.com \
--cc=msw@amazon.com \
--cc=nafea@amazon.com \
--cc=ndagan@amazon.com \
--cc=netanel@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=saeedb@amazon.com \
--cc=shayagr@amazon.com \
--cc=zorik@amazon.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.