From: Johannes Berg <johannes@sipsolutions.net>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 3/5] netlink: rework policy dump to support multiple policies
Date: Fri, 02 Oct 2020 22:38:49 +0200 [thread overview]
Message-ID: <185e714a1d205c3cdf0f655630f8c3edf552fc1a.camel@sipsolutions.net> (raw)
In-Reply-To: <20201002133720.7fb5818c@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On Fri, 2020-10-02 at 13:37 -0700, Jakub Kicinski wrote:
>
> I guess it's because of the volume of messages this would cause.
There's actually been a large cleanup, so it wouldn't be too bad.
I had really just suspected tooling/build system issues, you know which
C files you're compiling, but not easily which headers they're
including, so how to run the checker script on them?
Anyway, never really looked into it.
johannes
next prev parent reply other threads:[~2020-10-02 20:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 9:09 [PATCH 0/5] genetlink: complete policy dumping Johannes Berg
2020-10-02 9:09 ` [PATCH 1/5] netlink: simplify netlink_policy_dump_start() prototype Johannes Berg
2020-10-02 15:31 ` Jakub Kicinski
2020-10-02 20:02 ` Johannes Berg
2020-10-02 9:09 ` [PATCH 2/5] netlink: compare policy more accurately Johannes Berg
2020-10-02 15:39 ` Jakub Kicinski
2020-10-02 9:09 ` [PATCH 3/5] netlink: rework policy dump to support multiple policies Johannes Berg
2020-10-02 15:39 ` Jakub Kicinski
2020-10-02 20:11 ` Johannes Berg
2020-10-02 20:13 ` Johannes Berg
2020-10-02 20:37 ` Jakub Kicinski
2020-10-02 20:38 ` Johannes Berg [this message]
2020-10-02 20:42 ` Jakub Kicinski
2020-10-02 9:09 ` [PATCH 4/5] genetlink: factor skb preparation out of ctrl_dumppolicy() Johannes Berg
2020-10-02 15:42 ` Jakub Kicinski
2020-10-02 9:09 ` [PATCH 5/5] genetlink: properly support per-op policy dumping Johannes Berg
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=185e714a1d205c3cdf0f655630f8c3edf552fc1a.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=kuba@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.