DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Gao, DaxueX" <daxuex.gao@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>
Subject: RE: [PATCH] kernel/freebsd: fix module build on FreeBSD 14
Date: Fri, 22 Dec 2023 08:07:21 +0000	[thread overview]
Message-ID: <MW4PR11MB579946AA5BF3628EFD2756539D94A@MW4PR11MB5799.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20231219112959.10440-1-bruce.richardson@intel.com>

> -----Original Message-----
> From: Bruce Richardson <bruce.richardson@intel.com>
> Sent: Tuesday, December 19, 2023 7:30 PM
> To: dev@dpdk.org
> Cc: Richardson, Bruce <bruce.richardson@intel.com>
> Subject: [PATCH] kernel/freebsd: fix module build on FreeBSD 14
> 
> When building nic_uio module on FreeBSD 14, a build error is given in the
> DRIVER_MODULE macro:
> 
> .../nic_uio.c:84:81: error: too many arguments provided to function-like
> macro invocation DRIVER_MODULE(nic_uio, pci, nic_uio_driver,
> nic_uio_devclass, nic_uio_modevent, 0);
>                                                                                 ^ On FreeBSD 14, the devclass
> parameter is dropped from the macro, so we conditionally compile a different
> invocation for BSD versions before/ after v14.
> 
> Bugzilla Id: 1335
> 
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Tested-by: Daxue Gao <daxuex.gao@intel.com>

  reply	other threads:[~2023-12-22  8:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19 11:29 Bruce Richardson
2023-12-22  8:07 ` Gao, DaxueX [this message]
2024-01-31  9:49   ` Thomas Monjalon

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=MW4PR11MB579946AA5BF3628EFD2756539D94A@MW4PR11MB5799.namprd11.prod.outlook.com \
    --to=daxuex.gao@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.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).