From: Simon Horman <simon.horman@corigine.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH net-next v4 2/3] net: extend drop reasons for multiple subsystems
Date: Thu, 20 Apr 2023 17:20:40 +0200 [thread overview]
Message-ID: <ZEFYSMNsJVUeBqZ8@corigine.com> (raw)
In-Reply-To: <20230419125254.20789-2-johannes@sipsolutions.net>
On Wed, Apr 19, 2023 at 02:52:53PM +0200, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> Extend drop reasons to make them usable by subsystems
> other than core by reserving the high 16 bits for a
> new subsystem ID, of which 0 of course is used for the
> existing reasons immediately.
>
> To still be able to have string reasons, restructure
> that code a bit to make the loopup under RCU, the only
> user of this (right now) is drop_monitor.
Hi Johannes,
a minor nit from my side that you may want to address if you need
to re-spin for some other reason:
s/loopup/lookup/
next prev parent reply other threads:[~2023-04-20 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 12:52 [PATCH net-next v4 0/3] net: extend drop reasons Johannes Berg
2023-04-19 12:52 ` [PATCH net-next v4 1/3] net: move dropreason.h to dropreason-core.h Johannes Berg
2023-04-19 12:52 ` [PATCH net-next v4 2/3] net: extend drop reasons for multiple subsystems Johannes Berg
2023-04-20 15:20 ` Simon Horman [this message]
2023-04-19 12:52 ` [PATCH net-next v4 3/3] mac80211: use the new drop reasons infrastructure Johannes Berg
2023-04-20 15:21 ` Simon Horman
2023-04-21 3:40 ` [PATCH net-next v4 0/3] net: extend drop reasons patchwork-bot+netdevbpf
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=ZEFYSMNsJVUeBqZ8@corigine.com \
--to=simon.horman@corigine.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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.