All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
Cc: dev@dpdk.org, "Mattias Rönnblom" <hofors@lysator.liu.se>,
	"David Marchand" <david.marchand@redhat.com>,
	"Thomas Monjalon" <thomas@monjalon.net>,
	"Morten Brørup" <mb@smartsharesystems.com>
Subject: Re: [PATCH 3/3] bitset: promote API stable
Date: Thu, 22 Jan 2026 21:17:11 -0800	[thread overview]
Message-ID: <20260122211711.44710c70@phoenix.local> (raw)
In-Reply-To: <20250518080556.675092-3-mattias.ronnblom@ericsson.com>

On Sun, 18 May 2025 10:05:56 +0200
Mattias Rönnblom <mattias.ronnblom@ericsson.com> wrote:

> Remove experimental tag on the bitset API.
> 
> Signed-off-by: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
> ---

Acked-by: Stephen Hemminger <stephen@networkplumber.org>

AI review raised the question of whether change out of experimental needs
a release note, IMHO not.

Perhaps a script to change all the experimental API's from 24.11 or earlier
to stable (except tracing?) would be good idea.

  reply	other threads:[~2026-01-23  5:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-18  8:05 [PATCH 1/3] bitops: promote bit manipulation API to stable Mattias Rönnblom
2025-05-18  8:05 ` [PATCH 2/3] bitset: remove experimental bitops workaround Mattias Rönnblom
2026-01-23  5:15   ` Stephen Hemminger
2025-05-18  8:05 ` [PATCH 3/3] bitset: promote API stable Mattias Rönnblom
2026-01-23  5:17   ` Stephen Hemminger [this message]
2026-01-23  5:14 ` [PATCH 1/3] bitops: promote bit manipulation API to stable Stephen Hemminger

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=20260122211711.44710c70@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=hofors@lysator.liu.se \
    --cc=mattias.ronnblom@ericsson.com \
    --cc=mb@smartsharesystems.com \
    --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 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.