From: Stephen Hemminger <stephen@networkplumber.org>
To: Mike Bly <bly454@gmail.com>
Cc: dev@dpdk.org, stable@dpdk.org, jgrajcia@cisco.com
Subject: Re: [PATCH] net/memif: Fix memif-rx buffer linking
Date: Tue, 7 Jan 2025 08:48:33 -0800 [thread overview]
Message-ID: <20250107084833.65bd6998@pi5> (raw)
In-Reply-To: <CAB3eHOy3KS1LX3=7Vdy5aJ2V-0iGSHxXEFcRsHHWvO2LbZNKPg@mail.gmail.com>
On Mon, 6 Jan 2025 11:43:28 -0800
Mike Bly <bly454@gmail.com> wrote:
> From: Mike Bly <bly454@gmail.com>
> To: dev@dpdk.org
> Cc: stable@dpdk.org, jgrajcia@cisco.com
> Subject: [PATCH] net/memif: Fix memif-rx buffer linking
> Date: Mon, 6 Jan 2025 11:43:28 -0800
>
> Moving where dst_off is set in memif-rx function
> Bugzilla ID: 1609
> Fixes: aa17df860891 ("net/memif: add a Rx fast path")
> Cc: stable@dpdk.org
> Cc: Jakub Grajciar <jgrajcia@cisco.com>
>
> Signed-off-by: Mike Bly <bly454@gmail.com>
Please add more description (from bug report) about what the impact of this is.
Your description says what the change is but the next person looking at in two
years won't know why it was needed.
prev parent reply other threads:[~2025-01-07 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 19:43 Mike Bly
2025-01-07 16:48 ` Stephen Hemminger [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=20250107084833.65bd6998@pi5 \
--to=stephen@networkplumber.org \
--cc=bly454@gmail.com \
--cc=dev@dpdk.org \
--cc=jgrajcia@cisco.com \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).