From: Jiri Pirko <jiri@resnulli.us>
To: Pedro Tammela <pctammela@mojatatu.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, marcelo.leitner@gmail.com,
vladbu@nvidia.com
Subject: Re: [PATCH net-next v2 3/5] rtnl: add helper to send if skb is not null
Date: Tue, 5 Dec 2023 12:50:55 +0100 [thread overview]
Message-ID: <ZW8On8UhJLSttLtW@nanopsycho> (raw)
In-Reply-To: <20231204203907.413435-4-pctammela@mojatatu.com>
Mon, Dec 04, 2023 at 09:39:05PM CET, pctammela@mojatatu.com wrote:
>This is a convenience helper for routines handling conditional rtnl
>events, that is code that might send a notification depending on
>rtnl_has_listeners/rtnl_notify_needed.
>
>Instead of:
> if (skb)
> rtnetlink_send(...)
>
>Use:
> rtnetlink_maybe_send(...)
>
>Signed-off-by: Pedro Tammela <pctammela@mojatatu.com>
Reviewed-by: Jiri Pirko <jiri@nvidia.com>
next prev parent reply other threads:[~2023-12-05 11:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 20:39 [PATCH net-next v2 0/5] net/sched: conditional notification of events for cls and act Pedro Tammela
2023-12-04 20:39 ` [PATCH net-next v2 1/5] rtnl: add helper to check if rtnl group has listeners Pedro Tammela
2023-12-05 11:50 ` Jiri Pirko
2023-12-04 20:39 ` [PATCH net-next v2 2/5] rtnl: add helper to check if a notification is needed Pedro Tammela
2023-12-05 11:50 ` Jiri Pirko
2023-12-04 20:39 ` [PATCH net-next v2 3/5] rtnl: add helper to send if skb is not null Pedro Tammela
2023-12-05 11:50 ` Jiri Pirko [this message]
2023-12-04 20:39 ` [PATCH net-next v2 4/5] net/sched: act_api: conditional notification of events Pedro Tammela
2023-12-05 11:32 ` Jiri Pirko
2023-12-05 14:45 ` Pedro Tammela
2023-12-06 7:53 ` Jiri Pirko
2023-12-04 20:39 ` [PATCH net-next v2 5/5] net/sched: cls_api: " Pedro Tammela
2023-12-05 11:51 ` Jiri Pirko
2023-12-05 14:49 ` [PATCH net-next v2 0/5] net/sched: conditional notification of events for cls and act Pedro Tammela
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=ZW8On8UhJLSttLtW@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=kuba@kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.com \
--cc=vladbu@nvidia.com \
--cc=xiyou.wangcong@gmail.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.