From: Luca Boccassi <bluca@debian.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Jiri Slaby <jslaby@suse.cz>,
dev@dpdk.org, xuemingl@nvidia.com, ktraynor@redhat.com,
stable@dpdk.org
Subject: Re: [PATCH] kni: fix build with Linux 6.10
Date: Thu, 18 Jul 2024 10:28:13 +0100 [thread overview]
Message-ID: <CAMw=ZnRvycw=c2j-rcJeLTnqbA9rsX71Pbev=OFxEchkEWeU+Q@mail.gmail.com> (raw)
In-Reply-To: <2273498.iZASKD2KPV@thomas>
Hi Jiri,
Please follow the process described in the "stable release" paragraph at:
https://core.dpdk.org/contribute/
ie, one patch per affected LTS branch must be prepared, tested and
sent individually, and then we'll apply it. Thanks.
On Thu, 18 Jul 2024 at 10:16, Thomas Monjalon <thomas@monjalon.net> wrote:
>
> Adding stable@dpdk.org and LTS maintainers as Cc.
> It must be merged directly in LTS branches.
>
>
> 16/07/2024 10:44, Jiri Slaby:
> > 6.10 removed the "support" (it was never supported [1]) of separate
> > source and build dirs for out of tree modules.
> >
> > KNI uses "src=" hack for that purpose.
> >
> > Instead, copy sources to the build dir and don't rely upon the
> > unsupported...
> >
> > Intended esp. for stable/22.11. It should go wherever kni is still in
> > the tree.
> >
> > [1] https://lore.kernel.org/all/CAK7LNAQ47bZpE6c6Yoz-jQS78uU611oZwU8bH+7e=p5zSyADJw@mail.gmail.com/
> >
> > Signed-off-by: Jiri Slaby <jslaby@suse.cz>
> > ---
> > kernel/linux/kni/meson.build | 11 +++++++----
> > 1 file changed, 7 insertions(+), 4 deletions(-)
> >
> > diff --git a/kernel/linux/kni/meson.build b/kernel/linux/kni/meson.build
> > index 4c90069e..39ca2ade 100644
> > --- a/kernel/linux/kni/meson.build
> > +++ b/kernel/linux/kni/meson.build
> > @@ -11,8 +11,8 @@ if run_cmd.stdout().contains('txqueue') == true
> > kmod_cflags = '-DHAVE_ARG_TX_QUEUE'
> > endif
> >
> > -
> > -kni_mkfile = custom_target('rte_kni_makefile',
> > +kni_deps = []
> > +kni_deps += custom_target('rte_kni_makefile',
> > output: 'Makefile',
> > command: ['touch', '@OUTPUT@'])
> >
> > @@ -22,12 +22,15 @@ kni_sources = files(
> > 'Kbuild',
> > )
> >
> > +foreach file : kni_sources
> > + kni_deps += fs.copyfile(file)
> > +endforeach
> > +
> > custom_target('rte_kni',
> > input: kni_sources,
> > output: 'rte_kni.ko',
> > command: ['make', '-j4', '-C', kernel_build_dir,
> > 'M=' + meson.current_build_dir(),
> > - 'src=' + meson.current_source_dir(),
> > ' '.join(['MODULE_CFLAGS=', kmod_cflags,'-include '])
> > + dpdk_source_root + '/config/rte_config.h' +
> > ' -I' + dpdk_source_root + '/lib/eal/include' +
> > @@ -35,7 +38,7 @@ custom_target('rte_kni',
> > ' -I' + dpdk_build_root +
> > ' -I' + meson.current_source_dir(),
> > 'modules'] + cross_args,
> > - depends: kni_mkfile,
> > + depends: kni_deps,
> > install: install,
> > install_dir: kernel_install_dir,
> > build_by_default: get_option('enable_kmods'))
>
>
>
>
prev parent reply other threads:[~2024-07-18 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 8:44 Jiri Slaby
2024-07-18 9:16 ` Thomas Monjalon
2024-07-18 9:28 ` Luca Boccassi [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='CAMw=ZnRvycw=c2j-rcJeLTnqbA9rsX71Pbev=OFxEchkEWeU+Q@mail.gmail.com' \
--to=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=jslaby@suse.cz \
--cc=ktraynor@redhat.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=xuemingl@nvidia.com \
/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).