From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
intel-wired-lan@lists.osuosl.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Network Development <netdev@vger.kernel.org>,
jesse.brandeburg@intel.com,
Tony Nguyen <anthony.l.nguyen@intel.com>
Subject: Re: linux-next: Tree for Dec 15 (drivers/net/ethernet/intel/ice/ice_base.c)
Date: Fri, 15 Dec 2023 21:26:38 -0800 [thread overview]
Message-ID: <8b76dad3-8847-475b-aa17-613c9c978f7a@infradead.org> (raw)
In-Reply-To: <20231215150128.07763fb1@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 731 bytes --]
On 12/14/23 20:01, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20231214:
>
on s390:
# CONFIG_XDP_SOCKETS is not set
../drivers/net/ethernet/intel/ice/ice_base.c: In function 'ice_xsk_pool_fill_cb':
../drivers/net/ethernet/intel/ice/ice_base.c:533:16: error: variable 'desc' has initializer but incomplete type
533 | struct xsk_cb_desc desc = {};
| ^~~~~~~~~~~
../drivers/net/ethernet/intel/ice/ice_base.c:533:28: error: storage size of 'desc' isn't known
533 | struct xsk_cb_desc desc = {};
| ^~~~
Full randconfig file is attached.
--
#Randy
https://people.kernel.org/tglx/notes-about-netiquette
https://subspace.kernel.org/etiquette.html
[-- Attachment #2: config-r3916.gz --]
[-- Type: application/gzip, Size: 41457 bytes --]
next prev parent reply other threads:[~2023-12-16 5:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 4:01 linux-next: Tree for Dec 15 Stephen Rothwell
2023-12-16 5:26 ` Randy Dunlap [this message]
2023-12-18 17:29 ` linux-next: Tree for Dec 15 (drivers/net/ethernet/intel/ice/ice_base.c) Tony Nguyen
2023-12-16 5:29 ` linux-next: Tree for Dec 15 (fs/afs/) Randy Dunlap
2023-12-16 5:31 ` Randy Dunlap
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=8b76dad3-8847-475b-aa17-613c9c978f7a@infradead.org \
--to=rdunlap@infradead.org \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).