From: Stephen Hemminger <stephen@networkplumber.org>
To: Vipin P R <vipinp@vmware.com>
Cc: anatoly.burakov@intel.com, dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH] Memory Allocation: Adding a new UT for fb_array
Date: Mon, 16 Jan 2023 09:54:11 -0800 [thread overview]
Message-ID: <20230116095411.3ed168eb@hermes.local> (raw)
In-Reply-To: <1673615567-20873-2-git-send-email-vipinp@vmware.com>
On Fri, 13 Jan 2023 13:12:47 +0000
Vipin P R <vipinp@vmware.com> wrote:
> add test case coverage to cover the ms_idx jump
>
> Cc: stable@dpdk.org
>
> Signed-off-by: Vipin P R <vipinp@vmware.com>
> Acked-by: Kumara Parameshwaran <kparameshwar@vmware.com>
> ---
> Depends-on: 0001-Memory-Allocation-Fixes-ms_idx-jump-lookahead-during.patch
> Depends-on: 0002-Memory-Allocation-Fixes-ms_idx-jump-lookbehind-durin.patch
This looks like a good idea but lots of style errors on this patch.
Please run checkpatch, fix and resubmit.
next parent reply other threads:[~2023-01-16 17:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1673615567-20873-1-git-send-email-vipinp@vmware.com>
[not found] ` <1673615567-20873-2-git-send-email-vipinp@vmware.com>
2023-01-16 17:54 ` Stephen Hemminger [this message]
2023-05-16 13:39 ` Burakov, Anatoly
2023-05-16 14:25 ` Burakov, Anatoly
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=20230116095411.3ed168eb@hermes.local \
--to=stephen@networkplumber.org \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=vipinp@vmware.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).