All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH v1 0/2] Deprecation notices for VFIO
Date: Wed, 19 Nov 2025 10:43:43 +0000	[thread overview]
Message-ID: <aR2fX4LRIdOKlsKs@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <cover.1763548356.git.anatoly.burakov@intel.com>

On Wed, Nov 19, 2025 at 10:35:36AM +0000, Anatoly Burakov wrote:
> There's ongoing work to rework VFIO in DPDK [1]. These deprecation
> notices originally were part of that patchset, but were split off
> to easy review and acceptance.
> 
> [1] https://patches.dpdk.org/project/dpdk/list/?series=36746
> 
> Anatoly Burakov (2):
>   doc: add deprecation notice for VFIO API
>   doc: add deprecation notice for vDPA driver API
> 
>  doc/guides/rel_notes/deprecation.rst | 7 +++++++
>  1 file changed, 7 insertions(+)
>
Series-acked-by: Bruce Richardson <bruce.richardson@intel.com>

  parent reply	other threads:[~2025-11-19 10:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19 10:35 [PATCH v1 0/2] Deprecation notices for VFIO Anatoly Burakov
2025-11-19 10:35 ` [PATCH v1 1/2] doc: add deprecation notice for VFIO API Anatoly Burakov
2025-11-19 10:35 ` [PATCH v1 2/2] doc: add deprecation notice for vDPA driver API Anatoly Burakov
2025-11-19 10:43 ` Bruce Richardson [this message]
2026-02-26 13:59 ` [PATCH v2 0/2] Deprecation notices for VFIO Anatoly Burakov
2026-02-26 13:59   ` [PATCH v2 1/2] doc: add deprecation notice for VFIO API Anatoly Burakov
2026-03-05 14:35     ` David Marchand
2026-02-26 13:59   ` [PATCH v2 2/2] doc: add deprecation notice for vDPA driver API Anatoly Burakov
2026-03-05 14:36     ` David Marchand
2026-03-31 14:05   ` [PATCH v2 0/2] Deprecation notices for VFIO Thomas Monjalon

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=aR2fX4LRIdOKlsKs@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.