From: Bruce Richardson <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH 3/6] doc/rel_notes: keep library updates together
Date: Wed, 22 Jul 2026 08:59:20 +0100 [thread overview]
Message-ID: <amB4WC4XSIjsgSt6@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <wjhKUFwCR0mgQVZuWGEQ4w@monjalon.net>
On Tue, Jul 21, 2026 at 09:37:19PM +0200, Thomas Monjalon wrote:
> 21/07/2026 17:13, Bruce Richardson:
> > Group all library updates and enhancements together before driver
> > updates in the release notes.
>
> The suggested order in the release notes is:
> * Core libs (EAL, mempool, ring, mbuf, buses)
> * Device abstraction libs and PMDs (ordered alphabetically by vendor name)
> - ethdev (lib, PMDs)
> - cryptodev (lib, PMDs)
> - eventdev (lib, PMDs)
> - etc
> * Other libs
> * Apps, Examples, Tools (if significant)
>
> So it was placed here on purpose.
>
Ok, my bad. Drop this patch so.
/Bruce
next prev parent reply other threads:[~2026-07-22 7:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 15:13 [PATCH 0/6] doc/rel_notes: updates to 26.07 doc Bruce Richardson
2026-07-21 15:13 ` [PATCH 1/6] doc/rel_notes: remove bullets for single items Bruce Richardson
2026-07-21 15:13 ` [PATCH 2/6] doc/rel_notes: move mempool change to first item Bruce Richardson
2026-07-21 15:13 ` [PATCH 3/6] doc/rel_notes: keep library updates together Bruce Richardson
2026-07-21 19:37 ` Thomas Monjalon
2026-07-22 7:59 ` Bruce Richardson [this message]
2026-07-21 15:13 ` [PATCH 4/6] doc/rel_notes: fix driver ordering Bruce Richardson
2026-07-21 15:13 ` [PATCH 5/6] doc/rel_notes: fix style of API changes section Bruce Richardson
2026-07-21 15:13 ` [PATCH 6/6] doc/rel_notes: minor style fixes Bruce Richardson
2026-07-21 17:24 ` [PATCH 0/6] doc/rel_notes: updates to 26.07 doc Morten Brørup
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=amB4WC4XSIjsgSt6@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@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