From: Simon Horman <simon.horman@corigine.com>
To: Pedro Tammela <pctammela@mojatatu.com>
Cc: netdev@vger.kernel.org, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, jiri@resnulli.us, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net-next v3 5/5] net/sched: sch_qfq: BITify two bound definitions
Date: Fri, 21 Apr 2023 11:10:40 +0200 [thread overview]
Message-ID: <ZEJTEIMTK1d0+wWb@corigine.com> (raw)
In-Reply-To: <20230420164928.237235-6-pctammela@mojatatu.com>
On Thu, Apr 20, 2023 at 01:49:28PM -0300, Pedro Tammela wrote:
> For the sake of readability, change these two definitions to BIT()
> macros.
>
> Acked-by: Jamal Hadi Salim <jhs@mojatatu.com>
> Signed-off-by: Pedro Tammela <pctammela@mojatatu.com>
Reviewed-by: Simon Horman <simon.horman@corigine.com>
next prev parent reply other threads:[~2023-04-21 9:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 16:49 [PATCH net-next v3 0/5] net/sched: cleanup parsing prints in htb and qfq Pedro Tammela
2023-04-20 16:49 ` [PATCH net-next v3 1/5] net/sched: sch_htb: use extack on errors messages Pedro Tammela
2023-04-20 16:49 ` [PATCH net-next v3 2/5] net/sched: sch_qfq: " Pedro Tammela
2023-04-20 16:49 ` [PATCH net-next v3 3/5] net/sched: sch_qfq: refactor parsing of netlink parameters Pedro Tammela
2023-04-20 16:49 ` [PATCH net-next v3 4/5] selftests: tc-testing: add more tests for sch_qfq Pedro Tammela
2023-04-20 16:49 ` [PATCH net-next v3 5/5] net/sched: sch_qfq: BITify two bound definitions Pedro Tammela
2023-04-21 9:10 ` Simon Horman [this message]
2023-04-21 9:17 ` Eric Dumazet
2023-04-21 9:30 ` Simon Horman
2023-04-21 14:31 ` 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=ZEJTEIMTK1d0+wWb@corigine.com \
--to=simon.horman@corigine.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.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.