From: Yunsheng Lin <linyunsheng@huawei.com>
To: Eric Dumazet <edumazet@google.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: <netdev@vger.kernel.org>, <eric.dumazet@gmail.com>
Subject: Re: [PATCH net-next] net: remove enum skb_free_reason
Date: Tue, 7 Mar 2023 14:46:29 +0800 [thread overview]
Message-ID: <3139e94a-e438-afdb-dbed-d7ba069a0844@huawei.com> (raw)
In-Reply-To: <20230306204313.10492-1-edumazet@google.com>
On 2023/3/7 4:43, Eric Dumazet wrote:
> enum skb_drop_reason is more generic, we can adopt it instead.
>
> Provide dev_kfree_skb_irq_reason() and dev_kfree_skb_any_reason().
>
> This means drivers can use more precise drop reasons if they want to.
LGTM.
Reviewed-by: Yunsheng Lin <linyunsheng@huawei.com>
next prev parent reply other threads:[~2023-03-07 6:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 20:43 [PATCH net-next] net: remove enum skb_free_reason Eric Dumazet
2023-03-06 21:10 ` Simon Horman
2023-03-07 6:46 ` Yunsheng Lin [this message]
2023-03-08 8:20 ` 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=3139e94a-e438-afdb-dbed-d7ba069a0844@huawei.com \
--to=linyunsheng@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@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 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).