From: Bob Copeland <me@bobcopeland.com>
To: Jakub Kicinski <kubakici@wp.pl>
Cc: kbuild test robot <fengguang.wu@intel.com>,
"David S. Miller" <davem@davemloft.net>,
kbuild-all@01.org, netdev@vger.kernel.org
Subject: Re: [wireless-testsing2:master 1/4] drivers/net/netdevsim/bpf.c:130:14: sparse: incompatible types for 'case' statement
Date: Thu, 4 Jan 2018 10:56:29 -0500 [thread overview]
Message-ID: <20180104155628.k5lhb4fqyr2n2baa@localhost> (raw)
In-Reply-To: <20180103170237.0d682aa0@cakuba.netronome.com>
On Wed, Jan 03, 2018 at 05:02:37PM -0800, Jakub Kicinski wrote:
> > drivers/net/netdevsim/bpf.c: In function 'nsim_bpf_setup_tc_block_cb':
> > >> drivers/net/netdevsim/bpf.c:130:7: error: 'TC_CLSBPF_REPLACE' undeclared (first use in this function); did you mean 'TC_RED_REPLACE'?
> > case TC_CLSBPF_REPLACE:
> > ^~~~~~~~~~~~~~~~~
> > TC_RED_REPLACE
>
> FWIW looks like the tree contains old net-next code and latest net
> (linux/master) code. Pulling from net-next will solve this.
>
Thanks, yes, sorry about the noise. This tree doesn't always pull net-next,
but I'll do so and compile-test netdevsim in next build.
> > :::::: TO: Jakub Kicinski <jakub.kicinski@netronome.com>
> > :::::: CC: Daniel Borkmann <daniel@iogearbox.net>
>
> Interestingly Daniel and I were not CCed on the report, is this
> intentional?
One for kbuildbot team I guess, not sure how it determines whom to email.
Personally I would be ok if only myself and maybe linux-wireless got the
emails for this tree since most build failures are similar noise.
--
Bob Copeland %% https://bobcopeland.com/
next prev parent reply other threads:[~2018-01-04 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 19:53 [wireless-testsing2:master 1/4] drivers/net/netdevsim/bpf.c:130:14: sparse: incompatible types for 'case' statement kbuild test robot
2018-01-04 1:02 ` Jakub Kicinski
2018-01-04 15:56 ` Bob Copeland [this message]
2018-01-06 7:04 ` Fengguang Wu
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=20180104155628.k5lhb4fqyr2n2baa@localhost \
--to=me@bobcopeland.com \
--cc=davem@davemloft.net \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=kubakici@wp.pl \
--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