From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>,
Oz Shlomo <ozsh@mellanox.com>, Jiri Pirko <jiri@mellanox.com>
Subject: Re: [Patch net-next] net_sched: fold tcf_block_cb_call() into tc_setup_cb_call()
Date: Tue, 11 Dec 2018 16:25:49 -0800 [thread overview]
Message-ID: <20181211162549.7e0a879c@cakuba.netronome.com> (raw)
In-Reply-To: <CAM_iQpV3zR8aVNPnejFWRXUqibhaX+mTo88P3JCBLv2XpTWMew@mail.gmail.com>
On Tue, 11 Dec 2018 16:05:08 -0800, Cong Wang wrote:
> On Tue, Dec 11, 2018 at 1:44 PM Jakub Kicinski wrote:
> > On Tue, 11 Dec 2018 11:15:46 -0800, Cong Wang wrote:
> > > After commit 69bd48404f25 ("net/sched: Remove egdev mechanism"),
> > > tc_setup_cb_call() is nearly identical to tcf_block_cb_call(),
> > > so we can just fold tcf_block_cb_call() into tc_setup_cb_call()
> > > and remove its unused parameter 'exts'.
> > >
> > > Fixes: 69bd48404f25 ("net/sched: Remove egdev mechanism")
> > > Cc: Oz Shlomo <ozsh@mellanox.com>
> > > Cc: Jiri Pirko <jiri@mellanox.com>
> > > Signed-off-by: Cong Wang <xiyou.wangcong@gmail.com>
> >
> > Thanks, I didn't want to nit pick too much on Oz's patch :)
> >
> > The Fixes tag is superfluous, this is far from a bug, unnecessary noise
> > for backporters.
>
> Odd, you just Acked a patch which uses Fixes tag for a newline
> change:
>
> commit 10a5ce98539948affbdc28dc0f39a1b6b2307f9d
> Author: Martin KaFai Lau <kafai@fb.com>
> Date: Mon Dec 10 10:53:24 2018 -0800
>
> bpf: bpftool: Fix newline and p_err issue
>
> This patch fixes a few newline issues and also
> replaces p_err with p_info in prog.c
>
> Fixes: b053b439b72a ("bpf: libbpf: bpftool: Print bpf_line_info
> during prog dump")
> Cc: Jakub Kicinski <jakub.kicinski@netronome.com>
> Signed-off-by: Martin KaFai Lau <kafai@fb.com>
> Acked-by: Jakub Kicinski <jakub.kicinski@netronome.com>
> Signed-off-by: Alexei Starovoitov <ast@kernel.org>
>
> Jakub, please guide me which Jakub I should trust. :)
>
> Or you believe a newline change is more close to a bug fix
> than this?
>
> Please help!
p_err() breaks JSON so it's an actual bug.
next prev parent reply other threads:[~2018-12-12 0:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 19:15 [Patch net-next] net_sched: fold tcf_block_cb_call() into tc_setup_cb_call() Cong Wang
2018-12-11 21:44 ` Jakub Kicinski
2018-12-12 0:05 ` Cong Wang
2018-12-12 0:25 ` Jakub Kicinski [this message]
2018-12-12 0:32 ` Cong Wang
2018-12-12 6:51 ` Jiri Pirko
2018-12-12 11:31 ` Oz Shlomo
2018-12-14 23:32 ` David Miller
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=20181211162549.7e0a879c@cakuba.netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=jiri@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=ozsh@mellanox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox