From: Jakub Kicinski <kuba@kernel.org>
To: Samiullah Khawaja <skhawaja@google.com>
Cc: "David S . Miller " <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
almasrymina@google.com, willemb@google.com, jdamato@fastly.com,
mkarsten@uwaterloo.ca, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v6 3/5] net: define an enum for the napi threaded state
Date: Mon, 21 Jul 2025 16:48:56 -0700 [thread overview]
Message-ID: <20250721164856.1d2208e4@kernel.org> (raw)
In-Reply-To: <20250718232052.1266188-4-skhawaja@google.com>
On Fri, 18 Jul 2025 23:20:49 +0000 Samiullah Khawaja wrote:
> Documentation/netlink/specs/netdev.yaml | 13 ++++---
yamllint says:
91:15 error too many spaces inside brackets (brackets)
91:33 error too many spaces inside brackets (brackets)
Please fix, rebase (the series does not apply any more), and repost
the first 3 patches ASAP. We really need to merge the decoding of
threaded as enum before the merge window. We don't want it to be
a bare int in 6.17 and enum in 6.18. I may break some Python scripts.
--
pw-bot: cr
next prev parent reply other threads:[~2025-07-21 23:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 23:20 [PATCH net-next v6 0/5] Add support to do threaded napi busy poll Samiullah Khawaja
2025-07-18 23:20 ` [PATCH net-next v6 1/5] net: Create separate gro_flush_normal function Samiullah Khawaja
2025-07-18 23:20 ` [PATCH net-next v6 2/5] net: Use dev_set_threaded_hint instead of dev_set_threaded in drivers Samiullah Khawaja
2025-07-18 23:20 ` [PATCH net-next v6 3/5] net: define an enum for the napi threaded state Samiullah Khawaja
2025-07-21 23:48 ` Jakub Kicinski [this message]
2025-07-18 23:20 ` [PATCH net-next v6 4/5] Extend napi threaded polling to allow kthread based busy polling Samiullah Khawaja
2025-07-18 23:20 ` [PATCH net-next v6 5/5] selftests: Add napi threaded busy poll test in `busy_poller` Samiullah Khawaja
2025-07-19 21:27 ` [PATCH net-next v6 0/5] Add support to do threaded napi busy poll Martin Karsten
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=20250721164856.1d2208e4@kernel.org \
--to=kuba@kernel.org \
--cc=almasrymina@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jdamato@fastly.com \
--cc=mkarsten@uwaterloo.ca \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=skhawaja@google.com \
--cc=willemb@google.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.