From: Bruce Richardson <bruce.richardson@intel.com>
To: David Marchand <david.marchand@redhat.com>
Cc: <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH v3] build: remove deprecated kmods option
Date: Thu, 25 Sep 2025 09:42:07 +0100 [thread overview]
Message-ID: <aNUAX43vE-_0yW6R@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <aNQTUBumq7jnWqh0@bricha3-mobl1.ger.corp.intel.com>
On Wed, Sep 24, 2025 at 04:50:40PM +0100, Bruce Richardson wrote:
> On Wed, Sep 24, 2025 at 05:45:38PM +0200, David Marchand wrote:
> > On Tue, 23 Sept 2025 at 16:40, Bruce Richardson
> > <bruce.richardson@intel.com> wrote:
> > >
> > > The "enable_kmods" meson option was deprecated back in 2023[1], so can
> > > now be removed from DPDK.
> > >
> > > [1] https://doc.dpdk.org/guides-23.11/rel_notes/deprecation.html
> > >
> > > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> > > Acked-by: David Marchand <david.marchand@redhat.com>
> >
> > I see errors coming from Intel CI that requests enable_kmod option.
> > It needs to be fixed on Intel side so we can merge this series.
> >
> Yes. I've sent off a couple of hours ago a request to have that fixed in
> our CI. I'll let you know when I hear back.
>
> /Bruce
This has now been done, I'm told.
https://mails.dpdk.org/archives/test-report/2025-September/911620.html
/Bruce
next prev parent reply other threads:[~2025-09-25 8:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 7:57 [PATCH] " Bruce Richardson
2025-09-19 8:26 ` Bruce Richardson
2025-09-19 8:44 ` [PATCH v2] " Bruce Richardson
2025-09-19 8:55 ` David Marchand
2025-09-23 14:40 ` [PATCH v3] " Bruce Richardson
2025-09-24 15:45 ` David Marchand
2025-09-24 15:50 ` Bruce Richardson
2025-09-25 8:42 ` Bruce Richardson [this message]
2025-09-26 14:15 ` David Marchand
2025-09-26 14:15 ` David Marchand
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=aNUAX43vE-_0yW6R@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).