netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cong Wang <xiyou.wangcong@gmail.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org,
	Linux Kernel Network Developers <netdev@vger.kernel.org>,
	Jamal Hadi Salim <jhs@mojatatu.com>
Subject: Re: [Patch net-next 1/2] net_sched: move tc_action into tcf_common
Date: Thu, 21 Jul 2016 14:12:06 -0700	[thread overview]
Message-ID: <CAM_iQpUMXAyAUH32tfN4gYShPmEMpJCk1H3beT9FtvhK4cFMaQ@mail.gmail.com> (raw)
In-Reply-To: <201607220208.iT8LJ0gi%fengguang.wu@intel.com>

On Thu, Jul 21, 2016 at 11:35 AM, kbuild test robot <lkp@intel.com> wrote:
> All warnings (new ones prefixed by >>):
>
>    In file included from include/net/act_api.h:8:0,
>                     from net/sched/act_police.c:22:
>    net/sched/act_police.c: In function 'tcf_act_police_init':
>>> include/net/sch_generic.h:782:16: warning: 'police' may be used uninitialized in this function [-Wmaybe-uninitialized]
>      if (unlikely(r->linklayer == TC_LINKLAYER_ATM))
>                    ^
>    net/sched/act_police.c:125:21: note: 'police' was declared here
>      struct tcf_police *police;

Yeah, I need to move police = to_police(*a); down after the following
goto label.

I will update this patch after waiting for comments from Jamal.

  reply	other threads:[~2016-07-21 21:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-21  5:23 [Patch net-next 0/2] net_sched: refactor tc action structures Cong Wang
2016-07-21  5:23 ` [Patch net-next 1/2] net_sched: move tc_action into tcf_common Cong Wang
2016-07-21  7:38   ` Jamal Hadi Salim
2016-07-21 16:50     ` Cong Wang
2016-07-21 18:35   ` kbuild test robot
2016-07-21 21:12     ` Cong Wang [this message]
2016-07-21  5:23 ` [Patch net-next 2/2] net_sched: get rid of struct tcf_common Cong Wang

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=CAM_iQpUMXAyAUH32tfN4gYShPmEMpJCk1H3beT9FtvhK4cFMaQ@mail.gmail.com \
    --to=xiyou.wangcong@gmail.com \
    --cc=jhs@mojatatu.com \
    --cc=kbuild-all@01.org \
    --cc=lkp@intel.com \
    --cc=netdev@vger.kernel.org \
    /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).