DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Wan Junjie <wanjunjie@bytedance.com>, <dev@dpdk.org>
Cc: Chas Williams <chas3@att.com>, Min Hu <humin29@huawei.com>
Subject: Re: [PATCH v2 1/2] net/bonding: add error hint for invalid args
Date: Thu, 17 Feb 2022 11:57:44 +0000	[thread overview]
Message-ID: <ef8b7558-e152-4719-7bb1-3921974fd7fb@intel.com> (raw)
In-Reply-To: <8cfdd12a-3d5a-6bd6-25fa-10dbe4b92949@intel.com>

On 2/15/2022 11:56 AM, Ferruh Yigit wrote:
> On 2/15/2022 10:56 AM, Wan Junjie wrote:
>> When invalid args exist, application exits with no error hint.
>> Adding a log message here will help users to know the reason.
>>
>> Signed-off-by: Wan Junjie <wanjunjie@bytedance.com>
> 
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>

Series applied to dpdk-next-net/main, thanks.

  reply	other threads:[~2022-02-17 11:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14  8:13 [PATCH 1/2] net/bonding: add error hint for invald args Wan Junjie
2022-02-14  8:13 ` [PATCH 2/2] net/bonding: fix slaves initilizing on mtu setting Wan Junjie
2022-02-15  9:26   ` Min Hu (Connor)
2022-02-15 10:32     ` [External] " Wan Junjie
2022-02-15 10:59   ` [PATCH v2 2/2] net/bonding: fix slaves initializing " Wan Junjie
2022-02-16 13:22     ` Ferruh Yigit
2022-02-17  8:55       ` Min Hu (Connor)
2022-02-15  9:12 ` [PATCH 1/2] net/bonding: add error hint for invald args Min Hu (Connor)
2022-02-15  9:50   ` [External] " Wan Junjie
2022-02-15 10:56 ` [PATCH v2 1/2] net/bonding: add error hint for invalid args Wan Junjie
2022-02-15 11:56   ` Ferruh Yigit
2022-02-17 11:57     ` Ferruh Yigit [this message]
2022-02-16  0:29   ` Min Hu (Connor)

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=ef8b7558-e152-4719-7bb1-3921974fd7fb@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=chas3@att.com \
    --cc=dev@dpdk.org \
    --cc=humin29@huawei.com \
    --cc=wanjunjie@bytedance.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).