All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gur Stavi <gur.stavi@huawei.com>
To: Gur Stavi <gur.stavi@huawei.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>, Fan Gong <gongfan1@huawei.com>
Subject: [PATCH net-next v2 0/3] hinic3: queue_api related fixes
Date: Thu, 22 May 2025 09:54:40 +0300	[thread overview]
Message-ID: <cover.1747896423.git.gur.stavi@huawei.com> (raw)

This patch series contains improvement to queue_api and 2 queue_api
related patches to the hinic3 driver.

Changes:

v1: http://lore.kernel.org/netdev/cover.1747824040.git.gur.stavi@huawei.com

v2:
* Update cover letter subject and text.
* Add 2 patches for user code related to queue api.

Gur Stavi (3):
  queue_api: add subqueue variant netif_subqueue_sent
  hinic3: use netif_subqueue_sent api
  hinic3: remove tx_q name collision hack

 .../net/ethernet/huawei/hinic3/hinic3_tx.c    | 23 ++++++++-----------
 include/net/netdev_queues.h                   |  8 +++++++
 2 files changed, 18 insertions(+), 13 deletions(-)


base-commit: 3da895b23901964fcf23450f10b529d45069f333
-- 
2.45.2


             reply	other threads:[~2025-05-22  6:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-22  6:54 Gur Stavi [this message]
2025-05-22  6:54 ` [PATCH net-next v2 1/3] queue_api: add subqueue variant netif_subqueue_sent Gur Stavi
2025-05-27 10:06   ` Paolo Abeni
2025-05-22  6:54 ` [PATCH net-next v2 2/3] hinic3: use netif_subqueue_sent api Gur Stavi
2025-05-22  6:54 ` [PATCH net-next v2 3/3] hinic3: remove tx_q name collision hack Gur Stavi
2025-05-22 16:58 ` [PATCH net-next v2 0/3] hinic3: queue_api related fixes Jakub Kicinski

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=cover.1747896423.git.gur.stavi@huawei.com \
    --to=gur.stavi@huawei.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gongfan1@huawei.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.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.