From: Thomas Monjalon <thomas@monjalon.net>
To: "Chautru, Nicolas" <nicolas.chautru@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH v2] baseband/turbo_sw: Remove flexran_sdk meson option
Date: Wed, 29 Jun 2022 09:10:56 +0200 [thread overview]
Message-ID: <3775822.kdYZ1jHi8b@thomas> (raw)
In-Reply-To: <BY5PR11MB44510BC895BF638FDF03FC86F8BB9@BY5PR11MB4451.namprd11.prod.outlook.com>
29/06/2022 02:16, Chautru, Nicolas:
> > From: Thomas Monjalon <thomas@monjalon.net>
> >
> > 27/06/2022 22:29, Nicolas Chautru:
> > > Hi Thomas,
> > > This is change you requested earlier this year. This is targeting 22.11.
> >
> > OK thanks.
> >
> > > Basically we no longer pass a specific option but rely on pkgconfig.
> > > There is small change to generate the .pc files that Intel will make available
> > by end of year. Still the related change in DPDK is available now.
> >
> > It means we depend on a future version of Flexran?
> > Please could you document the minimum version?
>
> I expect the new version to be available in FlexRAN 22.11 (hence in November as well). Is that a concern?
One concern is to be able to test.
I guess it won't be an issue for you.
The other concern is to mandate the new version to the users.
I am fine with that as long as it is documented.
prev parent reply other threads:[~2022-06-29 7:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 20:29 Nicolas Chautru
2022-06-27 20:29 ` [PATCH v2] baseband/turbo_sw: remove Flexran SDK " Nicolas Chautru
2022-06-28 10:07 ` [PATCH v2] baseband/turbo_sw: Remove flexran_sdk " Thomas Monjalon
2022-06-29 0:16 ` Chautru, Nicolas
2022-06-29 7:10 ` Thomas Monjalon [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=3775822.kdYZ1jHi8b@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=nicolas.chautru@intel.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).