From: Jakub Kicinski <kuba@kernel.org>
To: Shinas Rasheed <srasheed@marvell.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<hgani@marvell.com>, <vimleshk@marvell.com>, <egallen@redhat.com>,
<mschmidt@redhat.com>, <pabeni@redhat.com>, <horms@kernel.org>,
<davem@davemloft.net>, <wizhao@redhat.com>, <konguyen@redhat.com>
Subject: Re: [PATCH net-next v3 0/4] Cleanup and optimizations to transmit code
Date: Sun, 29 Oct 2023 23:31:08 -0700 [thread overview]
Message-ID: <20231029233108.0bac2231@kernel.org> (raw)
In-Reply-To: <20231027121639.2382565-1-srasheed@marvell.com>
On Fri, 27 Oct 2023 05:16:35 -0700 Shinas Rasheed wrote:
> Pad small packets to ETH_ZLEN before transmit, cleanup dma sync calls,
> add xmit_more functionality and then further remove atomic
> variable usage in the prior.
## Form letter - net-next-closed
The merge window for v6.7 has begun and we have already posted our pull
request. Therefore net-next is closed for new drivers, features, code
refactoring and optimizations. We are currently accepting bug fixes only.
Please repost when net-next reopens after Nov 12th.
RFC patches sent for review only are obviously welcome at any time.
See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
--
pw-bot: defer
prev parent reply other threads:[~2023-10-30 6:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 12:16 [PATCH net-next v3 0/4] Cleanup and optimizations to transmit code Shinas Rasheed
2023-10-27 12:16 ` [PATCH net-next v3 1/4] octeon_ep: add padding for small packets Shinas Rasheed
2023-10-27 12:16 ` [PATCH net-next v3 2/4] octeon_ep: remove dma sync in trasmit path Shinas Rasheed
2023-10-27 12:16 ` [PATCH net-next v3 3/4] octeon_ep: implement xmit_more in transmit Shinas Rasheed
2023-10-27 12:16 ` [PATCH net-next v3 4/4] octeon_ep: remove atomic variable usage in Tx data path Shinas Rasheed
2023-10-30 6:31 ` Jakub Kicinski [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=20231029233108.0bac2231@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=egallen@redhat.com \
--cc=hgani@marvell.com \
--cc=horms@kernel.org \
--cc=konguyen@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=srasheed@marvell.com \
--cc=vimleshk@marvell.com \
--cc=wizhao@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;
as well as URLs for NNTP newsgroup(s).