From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
dev@dpdk.org, Matan Azrad <matan@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
Dariusz Sosnowski <dsosnowski@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>
Subject: Re: [PATCH] doc: remove Mellanox acquisition explanation
Date: Wed, 16 Jul 2025 09:17:12 -0700 [thread overview]
Message-ID: <20250716091712.77a64ef5@hermes.local> (raw)
In-Reply-To: <4667722.LvFx2qVVIh@thomas>
On Wed, 16 Jul 2025 17:56:04 +0200
Thomas Monjalon <thomas@monjalon.net> wrote:
> 16/07/2025 12:37, Bruce Richardson:
> > On Wed, Jul 16, 2025 at 12:15:16PM +0200, Thomas Monjalon wrote:
> > > Time has passed since Mellanox acquisition by NVIDIA.
> > > No need to explain this anymore.
> > >
> > > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> > > ---
> >
> > I wonder if we should include in DPDK a "future_cleanups" doc which
> > describes cleanups that can or should be done at specific points. For
> > example, after a specific release or date, or after we drop support for a
> > compiler or kernel version. After we add a workaround for a particular
> > tooling issue (or other change), it would be nice to have somewhere to
> > record when exactly the workaround can be removed and how/why to do so.
>
> It looks very programmatic :)
> Yes why not.
>
> In this case, there was no clear deadline.
>
>
There still are lots of experimental API's to make stable as well.
prev parent reply other threads:[~2025-07-16 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 10:15 Thomas Monjalon
2025-07-16 10:37 ` Bruce Richardson
2025-07-16 15:56 ` Thomas Monjalon
2025-07-16 16:17 ` Stephen Hemminger [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=20250716091712.77a64ef5@hermes.local \
--to=stephen@networkplumber.org \
--cc=bingz@nvidia.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@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).