From: Jakub Kicinski <kuba@kernel.org>
To: Gaurav Singh <gaurav1086@gmail.com>
Cc: Jamal Hadi Salim <jhs@mojatatu.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Jiri Pirko <jiri@resnulli.us>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org (open list:TC subsystem),
linux-kernel@vger.kernel.org (open list)
Subject: Re: [PATCH] [net/sched]: Remove redundant condition in qdisc_graft
Date: Wed, 17 Jun 2020 18:14:33 -0700 [thread overview]
Message-ID: <20200617181433.4aeee30c@kicinski-fedora-PC1C0HJN> (raw)
In-Reply-To: <20200618005526.27101-1-gaurav1086@gmail.com>
On Wed, 17 Jun 2020 20:55:26 -0400 Gaurav Singh wrote:
> parent cannot be NULL here since its in the else part
> of the if (parent == NULL) condition. Remove the extra
> check on parent pointer.
>
> Signed-off-by: Gaurav Singh <gaurav1086@gmail.com>
Change seems legit, but it obviously doesn't build...
> net/sched/sch_api.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/sched/sch_api.c b/net/sched/sch_api.c
> index 9a3449b56bd6..8c92d00c5c8e 100644
> --- a/net/sched/sch_api.c
> +++ b/net/sched/sch_api.c
> @@ -1094,7 +1094,7 @@ static int qdisc_graft(struct net_device *dev, struct Qdisc *parent,
>
> /* Only support running class lockless if parent is lockless */
> if (new && (new->flags & TCQ_F_NOLOCK) &&
> - parent && !(parent->flags & TCQ_F_NOLOCK))
> + && !(parent->flags & TCQ_F_NOLOCK))
> qdisc_clear_nolock(new);
>
> if (!cops || !cops->graft)
next prev parent reply other threads:[~2020-06-18 2:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 0:55 Gaurav Singh
2020-06-18 1:14 ` Jakub Kicinski [this message]
2020-06-18 1:23 ` Gaurav Singh
2020-06-18 3:43 ` Eric Dumazet
2020-06-18 4:00 ` Gaurav Singh
2020-06-18 14:53 ` David Miller
2020-06-18 20:36 ` Gaurav Singh
2020-06-21 0:30 ` David Miller
2020-06-18 6:05 ` kernel test robot
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=20200617181433.4aeee30c@kicinski-fedora-PC1C0HJN \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=gaurav1086@gmail.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®