netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Vasundhara Volam <vasundhara-v.volam@broadcom.com>
Cc: David Miller <davem@davemloft.net>,
	"michael.chan@broadcom.com" <michael.chan@broadcom.com>,
	Jiri Pirko <jiri@mellanox.com>, Netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next RFC 1/7] devlink: Add devlink_param for port register and unregister
Date: Mon, 10 Dec 2018 12:29:34 +0100	[thread overview]
Message-ID: <20181210112934.GA2058@nanopsycho> (raw)
In-Reply-To: <CAACQVJrn5vAbqJnCBVj=zAssy2wZgCE8VaJy8EJ9fj2MKiTMKw@mail.gmail.com>

Mon, Dec 10, 2018 at 10:21:03AM CET, vasundhara-v.volam@broadcom.com wrote:
>On Wed, Dec 5, 2018 at 5:24 PM Jiri Pirko <jiri@resnulli.us> wrote:
>>
>> Wed, Dec 05, 2018 at 06:56:54AM CET, vasundhara-v.volam@broadcom.com wrote:

[...]

>> >+      mutex_lock(&devlink->lock);
>> >+      for (i = 0; i < params_count; i++) {
>> >+              if (!param || !param->name || !param->supported_cmodes) {
>> >+                      err = -EINVAL;
>> >+                      goto rollback;
>> >+              }
>> >+              if (param->generic) {
>> >+                      err = devlink_port_param_generic_verify(param);
>> >+                      if (err)
>> >+                              goto rollback;
>> >+              } else {
>> >+                      err = devlink_port_param_driver_verify(param);
>>
>> This is duplicated code from devlink_params_register(). Once you use a
>> single enum for all params, you can push this into a common function for
>> both devlink_params_register() and devlink_port_params_register()
>Jiri, you are referring to move only param verification code into a
>common function. right?

Once you will have a single enum, you need only one verify() function.

  reply	other threads:[~2018-12-10 11:36 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-05  5:56 [PATCH net-next RFC 0/7] Add configuration parameters support for devlink_port Vasundhara Volam
2018-12-05  5:56 ` [PATCH net-next RFC 1/7] devlink: Add devlink_param for port register and unregister Vasundhara Volam
2018-12-05 11:47   ` Jiri Pirko
2018-12-06  6:02     ` Vasundhara Volam
2018-12-06  7:06       ` Jiri Pirko
2018-12-06  7:26         ` Vasundhara Volam
2018-12-10  9:21     ` Vasundhara Volam
2018-12-10 11:29       ` Jiri Pirko [this message]
2018-12-05  5:56 ` [PATCH net-next RFC 2/7] devlink: Add port param get command Vasundhara Volam
2018-12-05 11:51   ` Jiri Pirko
2018-12-05  5:56 ` [PATCH net-next RFC 3/7] devlink: Add port param set command Vasundhara Volam
2018-12-05 12:13   ` Jiri Pirko
2018-12-05  5:56 ` [PATCH net-next RFC 4/7] devlink: Add support for get/set driverinit value for devlink_port Vasundhara Volam
2018-12-05 12:59   ` Jiri Pirko
2018-12-05  5:56 ` [PATCH net-next RFC 5/7] devlink: Add devlink notifications support for port params Vasundhara Volam
2018-12-05 13:02   ` Jiri Pirko
2018-12-05  5:56 ` [PATCH net-next RFC 6/7] devlink: Add a boolean generic port parameter Vasundhara Volam
2018-12-05 13:04   ` Jiri Pirko
2018-12-05  5:57 ` [PATCH net-next RFC 7/7] bnxt_en: Add bnxt_en initial port params table and register it Vasundhara Volam
2018-12-05 13:05   ` Jiri Pirko
2018-12-05 23:33   ` Jakub Kicinski
2018-12-06  0:01     ` Michael Chan
2018-12-06  0:42       ` Jakub Kicinski
2018-12-06  1:18         ` Michael Chan
2018-12-06  6:00           ` Jakub Kicinski
2018-12-06  6:41             ` Michael Chan
2018-12-06  7:11               ` Jakub Kicinski
2018-12-06  8:57                 ` Michael Chan
2018-12-06  9:03                   ` Jiri Pirko
2018-12-06 10:31                     ` Vasundhara Volam
2018-12-06 11:11                       ` Jiri Pirko
2018-12-06 10:36                   ` Jakub Kicinski
2018-12-06 11:00                     ` Michael Chan

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=20181210112934.GA2058@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=davem@davemloft.net \
    --cc=jiri@mellanox.com \
    --cc=michael.chan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=vasundhara-v.volam@broadcom.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).