From: Bruce Richardson <bruce.richardson@intel.com>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: David Marchand <david.marchand@redhat.com>,
Luca Boccassi <bluca@debian.org>,
Thomas Monjalon <thomas@monjalon.net>, <dev@dpdk.org>,
<stable@dpdk.org>, Conor Walsh <conor.walsh@intel.com>,
Kevin Laatz <kevin.laatz@intel.com>
Subject: Re: [PATCH] dma/idxd: remove experimental on whole driver
Date: Fri, 9 Oct 2026 11:57:42 +0100 [thread overview]
Message-ID: <asjIppnLn90ikKtg@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <4849aff4-5c19-4676-b94d-f8ad393cecbf@redhat.com>
On Fri, Oct 09, 2026 at 10:52:50AM +0100, Kevin Traynor wrote:
> On 10/9/26 10:03, Bruce Richardson wrote:
> > On Fri, Oct 09, 2026 at 10:55:49AM +0200, David Marchand wrote:
> > > On Thu, 8 Oct 2026 at 17:44, Bruce Richardson
> > > <bruce.richardson@intel.com> wrote:
> > > >
> > > > The idxd DMA driver was marked as experimental in MAINTAINERS file.
> > > > Remove this designation as it's been stable for a long time now.
> > > >
> > > > Fixes: e33ad06eaeeb ("dma/idxd: add skeleton for VFIO based DSA device")
> > > > Cc: stable@dpdk.org
> > > >
> > > > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> > > > ---
> > > >
> > > > Putting the fixline as the original start of the driver implementation,
> > > > since there is no good commit point to use to identify the stabilization
> > > > of the driver. Since this change should be good to backport to all
> > > > currently supported LTS releases, the orignal addition of the driver
> > > > works fine as a commit being fixed.
> > >
> > > No opinion on the backporting aspect.
> > > At least the driver looks stable for a while, so the patch lgtm.
> > >
> > Given that the driver has been around since 2021 and the oldest supported
> > LTS is 23.11, I felt it worthwhile to backport. However, if LTS
> > maintainers want to avoid this patch, I'm not too concerned :-)
>
> We're saying the main branch is non-experimental _now_ but it has diverged
> from what is in LTS branches e.g. [0]
>
> I think it would be better not to backport this patch to LTS as the driver
> was released as experimental in those releases and the docs reflect that.
>
> That it is changing in main is positive :-) but it doesn't seem worth
> evaluating each LTS branch and backports (and any other code context) to say
> if could now say that about the LTS branch too and retro-fitting the docs.
>
Sure, no problem.
prev parent reply other threads:[~2026-10-09 10:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 15:43 [PATCH] dma/idxd: remove experimental on whole driver Bruce Richardson
2026-10-09 8:55 ` David Marchand
2026-10-09 9:03 ` Bruce Richardson
2026-10-09 9:52 ` Kevin Traynor
2026-10-09 10:57 ` Bruce Richardson [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=asjIppnLn90ikKtg@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=bluca@debian.org \
--cc=conor.walsh@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=kevin.laatz@intel.com \
--cc=ktraynor@redhat.com \
--cc=stable@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