All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Jianguo Wu <wujianguo106@163.com>
Cc: netdev@vger.kernel.org, shemminger@linux-foundation.org,
	noureddine@arista.com, Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH] net-procfs: show net devices bound packet types
Date: Thu, 20 Jan 2022 07:58:15 -0800	[thread overview]
Message-ID: <20220120075815.1aeb87c5@hermes.local> (raw)
In-Reply-To: <04a03a41-6d44-645e-4935-613de20afb2d@163.com>

On Thu, 20 Jan 2022 15:04:58 +0800
Jianguo Wu <wujianguo106@163.com> wrote:

> From: wujianguo <wujianguo@chinatelecom.cn>
> 
> After commit:7866a621043f ("dev: add per net_device packet type chains"),
> we can not get packet types that are bound to a specified net device.

That is an API regression, why not fix that rather than adding new /proc API?

/proc API's are legacy and it would be best not to add more there.

      reply	other threads:[~2022-01-20 15:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-20  7:04 [PATCH] net-procfs: show net devices bound packet types Jianguo Wu
2022-01-20 15:58 ` Stephen Hemminger [this message]

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=20220120075815.1aeb87c5@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=noureddine@arista.com \
    --cc=shemminger@linux-foundation.org \
    --cc=wujianguo106@163.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.