From: Thomas Monjalon <thomas@monjalon.net>
To: "Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Gao, DaxueX" <daxuex.gao@intel.com>,
stable@dpdk.org
Subject: Re: [PATCH] kernel/freebsd: fix module build on FreeBSD 14
Date: Wed, 31 Jan 2024 10:49:21 +0100 [thread overview]
Message-ID: <2103024.K71DO8KEF6@thomas> (raw)
In-Reply-To: <MW4PR11MB579946AA5BF3628EFD2756539D94A@MW4PR11MB5799.namprd11.prod.outlook.com>
> > 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
Id -> ID
> >
> > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> Tested-by: Daxue Gao <daxuex.gao@intel.com>
+Cc: stable@dpdk.org
Applied, thanks.
parent reply other threads:[~2024-01-31 9:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <MW4PR11MB579946AA5BF3628EFD2756539D94A@MW4PR11MB5799.namprd11.prod.outlook.com>]
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=2103024.K71DO8KEF6@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=daxuex.gao@intel.com \
--cc=dev@dpdk.org \
--cc=stable@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).