From: Olivier MATZ <olivier.matz@6wind.com>
To: "Ilya V. Matveychikov" <matvejchikov@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] mbuf: cleanup rte_pktmbuf_lastseg function
Date: Thu, 14 Dec 2017 10:30:11 +0100 [thread overview]
Message-ID: <20171214093009.wuhe23x7lfy4jwhq@platinum> (raw)
In-Reply-To: <20171214084827.356wg4dyhu7i24xu@platinum>
On Thu, Dec 14, 2017 at 09:48:29AM +0100, Olivier MATZ wrote:
> On Sun, Dec 10, 2017 at 12:08:22AM +0300, Ilya V. Matveychikov wrote:
> > There is no reason to have local variable m2.
> >
> > Fixes: af75078fece3 ("first public release")
> > Signed-off-by: Ilya V. Matveychikov <matvejchikov@gmail.com>
>
> Acked-by: Olivier Matz <olivier.matz@6wind.com>
Just realized the title does not match ./devtools/check-git-log.sh
constraints. I suggest instead:
mbuf: cleanup function to get last segment
next prev parent reply other threads:[~2017-12-14 9:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 13:44 [dpdk-dev] [PATCH] mbuf: cleanup rte_pktmbuf_lastseg(), remove useless variable Ilya Matveychikov
2017-11-14 20:32 ` Hanoch Haim (hhaim)
2017-11-14 20:50 ` Ilya Matveychikov
2017-12-01 16:36 ` Olivier MATZ
2017-12-09 21:08 ` [dpdk-dev] [PATCH v2] mbuf: cleanup rte_pktmbuf_lastseg function Ilya V. Matveychikov
2017-12-14 8:48 ` Olivier MATZ
2017-12-14 9:30 ` Olivier MATZ [this message]
2018-01-11 23:21 ` 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=20171214093009.wuhe23x7lfy4jwhq@platinum \
--to=olivier.matz@6wind.com \
--cc=dev@dpdk.org \
--cc=matvejchikov@gmail.com \
/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).