public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: <dev@dpdk.org>,
	"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>,
	<bruce.richardson@intel.com>
Subject: Re: [PATCH v2] ethdev: clarify rte_eth_tx_burst() return value and ownership semantics
Date: Thu, 19 Feb 2026 11:00:15 -0800	[thread overview]
Message-ID: <20260219110015.142bcdd3@phoenix.local> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35F6572C@smartserver.smartshare.dk>

On Thu, 19 Feb 2026 08:20:44 +0100
Morten Brørup <mb@smartsharesystems.com> wrote:

> > + * If a packet cannot be transmitted due to an error (for example, an
> > + * invalid offload flag), the driver must still consume it and free
> > the
> > + * mbuf, rather than stopping at that point. Such packets should be
> > + * counted in the *tx_errors* port statistic.
> > + *  
> 
> Looks like v1.
> Please update with my feedback.
> 
> -Morten


Thanks missed that in re-edit

  reply	other threads:[~2026-02-19 19:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-16 18:00 [RFC] ethdev: clarify rte_eth_tx_burst() return value and ownership semantics Stephen Hemminger
2026-02-17  6:41 ` Andrew Rybchenko
2026-02-17 14:54   ` Stephen Hemminger
2026-02-18  8:48 ` Morten Brørup
2026-02-18  8:52   ` Bruce Richardson
2026-02-18 17:13   ` Stephen Hemminger
2026-02-18 17:32     ` Morten Brørup
2026-02-19  0:44 ` [PATCH v2] " Stephen Hemminger
2026-02-19  7:20   ` Morten Brørup
2026-02-19 19:00     ` Stephen Hemminger [this message]
2026-02-19 19:00   ` Stephen Hemminger

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=20260219110015.142bcdd3@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=mb@smartsharesystems.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