From: Stephen Hemminger <stephen@networkplumber.org>
To: "Martin Špinler" <spinler@cesnet.cz>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2] doc/nfb: update release notes for nfb driver
Date: Mon, 2 Feb 2026 12:17:43 -0800 [thread overview]
Message-ID: <20260202121743.53ad004e@phoenix.local> (raw)
In-Reply-To: <811bfe37111be369a9aba35c49d705fd74f4ea54.camel@cesnet.cz>
On Mon, 02 Feb 2026 21:14:58 +0100
Martin Špinler <spinler@cesnet.cz> wrote:
> On Mon, 2026-02-02 at 21:12 +0100, spinler@cesnet.cz wrote:
> > Update the release notes for the NFB driver
> > with the timestamp value changes.
>
> This release notes update should have been in series-37064 ("net/nfb:
> code cleanup").
> (And certainly not in "net/nfb: rework to real multiport" series, as
> you pointed right).
>
> But as the "net/nfb: code cleanup" was already nearly upstreamed, I
> didn't dare to modify them with this patch.
No worries. As long as the total version has the right release notes.
I don't worry too much about getting the release note exactly matched
with the patch.
next prev parent reply other threads:[~2026-02-02 20:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 15:15 [PATCH] doc/nfb: update release notes for nfb driver spinler
2026-02-02 20:12 ` [PATCH v2] " spinler
2026-02-02 20:14 ` Martin Špinler
2026-02-02 20:17 ` Stephen Hemminger [this message]
2026-02-10 18:41 ` 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=20260202121743.53ad004e@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=spinler@cesnet.cz \
/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