From: David Miller <davem@davemloft.net>
To: mrv@mojatatu.com
Cc: netdev@vger.kernel.org, kernel@mojatatu.com, jhs@mojatatu.com,
jiri@resnulli.us, xiyou.wangcong@gmail.com
Subject: Re: [PATCH net-next 1/5] net sched actions: routines to calculate common TLVs size
Date: Mon, 05 Mar 2018 10:00:19 -0500 (EST) [thread overview]
Message-ID: <20180305.100019.2202856913464554326.davem@davemloft.net> (raw)
In-Reply-To: <1520028103-14878-2-git-send-email-mrv@mojatatu.com>
From: Roman Mashak <mrv@mojatatu.com>
Date: Fri, 2 Mar 2018 17:01:39 -0500
> Introduce routine to calculate size of the common tc netlink attributes,
> and another helper routine to get the full message size including netlink
> header and service header.
>
> Signed-off-by: Roman Mashak <mrv@mojatatu.com>
Adding the helpers as static functions, with no users, makes this
series non-bisectable because the compiler will warn about the unused
functions at this point in the series.
next prev parent reply other threads:[~2018-03-05 15:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 22:01 [PATCH net-next 0/5] Fix event generation for actions batch Add/Delete mode Roman Mashak
2018-03-02 22:01 ` [PATCH net-next 1/5] net sched actions: routines to calculate common TLVs size Roman Mashak
2018-03-05 15:00 ` David Miller [this message]
2018-03-05 15:45 ` Roman Mashak
2018-03-02 22:01 ` [PATCH net-next 2/5] net sched actions: add new tc_action_ops callback Roman Mashak
2018-03-05 15:00 ` David Miller
2018-03-05 15:46 ` Roman Mashak
2018-03-02 22:01 ` [PATCH net-next 3/5] net sched actions: calculate add/delete event message size Roman Mashak
2018-03-02 22:01 ` [PATCH net-next 4/5] net sched actions: implement get_fill_size routine in act_gact Roman Mashak
2018-03-02 22:01 ` [PATCH net-next 5/5] net sched actions: implement get_fill_size routine in act_police Roman Mashak
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=20180305.100019.2202856913464554326.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kernel@mojatatu.com \
--cc=mrv@mojatatu.com \
--cc=netdev@vger.kernel.org \
--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 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).