From: Guillaume Nault <gnault@redhat.com>
To: kbuild test robot <lkp@intel.com>
Cc: David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
kbuild-all@lists.01.org, netdev@vger.kernel.org,
Jamal Hadi Salim <jhs@mojatatu.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Jiri Pirko <jiri@mellanox.com>,
Benjamin LaHaise <benjamin.lahaise@netronome.com>,
Tom Herbert <tom@herbertland.com>,
Liel Shoshan <liels@mellanox.com>,
Rony Efraim <ronye@mellanox.com>
Subject: Re: [PATCH net-next 1/2] flow_dissector: Parse multiple MPLS Label Stack Entries
Date: Thu, 21 May 2020 12:09:02 +0200 [thread overview]
Message-ID: <20200521100902.GA24550@pc-3.home> (raw)
In-Reply-To: <202005210931.kHcrKMdv%lkp@intel.com>
On Thu, May 21, 2020 at 09:24:25AM +0800, kbuild test robot wrote:
> All errors (new ones prefixed by >>, old ones prefixed by <<):
>
> In file included from include/linux/build_bug.h:5,
> from include/linux/bitfield.h:10,
> from drivers/net/ethernet/netronome/nfp/flower/match.c:4:
> drivers/net/ethernet/netronome/nfp/flower/match.c: In function 'nfp_flower_compile_mac':
> >> drivers/net/ethernet/netronome/nfp/flower/match.c:100:57: error: 'struct flow_dissector_key_mpls' has no member named 'mpls_label'
>
Sorry, I didn't realise this was used by NFP.
I'll respin.
next prev parent reply other threads:[~2020-05-21 10:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 17:28 [PATCH net-next 0/2] flow_dissector, cls_flower: Add support for multiple MPLS Label Stack Entries Guillaume Nault
2020-05-20 17:28 ` [PATCH net-next 1/2] flow_dissector: Parse " Guillaume Nault
2020-05-21 1:24 ` kbuild test robot
2020-05-21 10:09 ` Guillaume Nault [this message]
2020-05-21 11:54 ` kbuild test robot
2020-05-20 17:28 ` [PATCH net-next 2/2] cls_flower: Support filtering on " Guillaume Nault
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=20200521100902.GA24550@pc-3.home \
--to=gnault@redhat.com \
--cc=benjamin.lahaise@netronome.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=jiri@mellanox.com \
--cc=kbuild-all@lists.01.org \
--cc=kuba@kernel.org \
--cc=liels@mellanox.com \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=ronye@mellanox.com \
--cc=tom@herbertland.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;
as well as URLs for NNTP newsgroup(s).