DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
To: Matan Azrad <matan@mellanox.com>
Cc: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/2] net/mlx5: support device removal event
Date: Fri, 25 Aug 2017 10:29:18 +0200	[thread overview]
Message-ID: <20170825082918.GU4544@autoinstall.dev.6wind.com> (raw)
In-Reply-To: <DB6PR0502MB3048B8F6B8E1A4B1360F0C87D29A0@DB6PR0502MB3048.eurprd05.prod.outlook.com>

On Thu, Aug 24, 2017 at 02:33:43PM +0000, Matan Azrad wrote:
> Hi Nelio
>[...] 
> > 
> > I am expecting to find something related to a link update, what I see is an
> > alarm update.  I don't expect to update an alarm but a link.  The names and
> > action are inconsistent i.e. mlx5_dev_link_status_handler() should handle a
> > link not an alarm.
> > 
> > I understand there is a need to add more function levels, but the
> > priv_link_status_alarm_update() should be renamed to something like
> > priv_link_status_update().
> 
> OK, I think I understand you.
> 
> Because the alarm is a workaround you don't think it should be mentioned
> in function description or function name.
> (also the function subject should be the link status and not the alarm)
> I can agree with you about it.
> And I will create v2 with your suggestion - priv_link_status_update.

Thanks,

> The return value description can stay as in old code semantic:
> Zero if the callback process can be called immediately.
> 
> Are you agree?

Yes.

> Maybe we can tell something about the alarm and inconsistent reason
> In this function description or internal comment for future code review.
> If you want it, please suggest comment.

Yes the comment can added internally.

Thanks,

-- 
Nélio Laranjeiro
6WIND

  reply	other threads:[~2017-08-25  8:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-13 12:25 Matan Azrad
2017-08-13 12:25 ` [dpdk-dev] [PATCH 2/2] net/mlx5: fix probe failure report Matan Azrad
2017-08-23  9:44   ` Nélio Laranjeiro
2017-09-01 10:40     ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2017-08-23  9:40 ` [dpdk-dev] [PATCH 1/2] net/mlx5: support device removal event Nélio Laranjeiro
2017-08-23 19:44   ` Matan Azrad
2017-08-24  7:38     ` Nélio Laranjeiro
2017-08-24 14:33       ` Matan Azrad
2017-08-25  8:29         ` Nélio Laranjeiro [this message]
2017-08-29  8:30           ` [dpdk-dev] [PATCH v2] " Matan Azrad
2017-09-04 12:49             ` Nélio Laranjeiro
2017-09-04 13:55               ` [dpdk-dev] [PATCH v3] " Matan Azrad
2017-09-04 15:33                 ` Adrien Mazarguil
2017-09-04 17:52                   ` Matan Azrad
2017-09-05  9:28                     ` Adrien Mazarguil
2017-09-05 10:38                       ` Matan Azrad
2017-09-05 12:01                         ` Adrien Mazarguil
2017-09-05 13:36                           ` Matan Azrad
2017-09-06  7:12                             ` Adrien Mazarguil

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=20170825082918.GU4544@autoinstall.dev.6wind.com \
    --to=nelio.laranjeiro@6wind.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=matan@mellanox.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).