From: Jakub Kicinski <kuba@kernel.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Network Development <netdev@vger.kernel.org>,
bpf <bpf@vger.kernel.org>,
Jesper Dangaard Brouer <hawk@kernel.org>,
Amritha Nambiar <amritha.nambiar@intel.com>,
Alexander Lobakin <aleksander.lobakin@intel.com>
Subject: Re: [PATCH bpf-next 0/3] net: struct netdev_rx_queue and xdp.h reshuffling
Date: Tue, 1 Aug 2023 20:11:53 -0700 [thread overview]
Message-ID: <20230801201153.0b81d551@kernel.org> (raw)
In-Reply-To: <CAADnVQJdA25VBE+7Erw7-beL4+=fy1KtRA3ojN0o1yUztnyjjw@mail.gmail.com>
On Tue, 1 Aug 2023 19:31:25 -0700 Alexei Starovoitov wrote:
> Especially considering that targeting bpf-next will exercise BPF CI...
> and it's not happy at the moment:
> ../net/netfilter/nf_conntrack_bpf.c: In function ‘bpf_xdp_ct_alloc’:
> ../net/netfilter/nf_conntrack_bpf.c:258:44: error: dereferencing
> pointer to incomplete type ‘struct xdp_buff’
> 258 | nfct = __bpf_nf_ct_alloc_entry(dev_net(ctx->rxq->dev),
> bpf_tuple, tuple__sz,
> |
ugh, will fix. allmodconfig apparently doesn't enable all of BPF :(
prev parent reply other threads:[~2023-08-02 3:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 0:32 [PATCH bpf-next 0/3] net: struct netdev_rx_queue and xdp.h reshuffling Jakub Kicinski
2023-08-02 0:32 ` [PATCH bpf-next 1/3] eth: add missing xdp.h includes in drivers Jakub Kicinski
2023-08-02 2:26 ` Wei Fang
2023-08-02 16:00 ` Alexander Lobakin
2023-08-02 18:06 ` Gerhard Engleder
2023-08-02 0:32 ` [PATCH bpf-next 2/3] net: move struct netdev_rx_queue out of netdevice.h Jakub Kicinski
2023-08-02 19:42 ` Nambiar, Amritha
2023-08-02 0:32 ` [PATCH bpf-next 3/3] net: invert the netdevice.h vs xdp.h dependency Jakub Kicinski
2023-08-02 2:31 ` [PATCH bpf-next 0/3] net: struct netdev_rx_queue and xdp.h reshuffling Alexei Starovoitov
2023-08-02 3:11 ` Jakub Kicinski [this message]
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=20230801201153.0b81d551@kernel.org \
--to=kuba@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=alexei.starovoitov@gmail.com \
--cc=amritha.nambiar@intel.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=hawk@kernel.org \
--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).