From: David Miller <davem@davemloft.net>
To: jiri@resnulli.us
Cc: vasundhara-v.volam@broadcom.com, gerlitz.or@gmail.com,
michael.chan@broadcom.com, netdev@vger.kernel.org,
jiri@mellanox.com, jakub.kicinski@netronome.com
Subject: Re: [PATCH v4 net-next 0/9] bnxt_en: devlink param updates
Date: Thu, 04 Oct 2018 13:50:21 -0700 (PDT) [thread overview]
Message-ID: <20181004.135021.719953370786213619.davem@davemloft.net> (raw)
In-Reply-To: <20181004103940.GE2222@nanopsycho>
From: Jiri Pirko <jiri@resnulli.us>
Date: Thu, 4 Oct 2018 12:39:40 +0200
> Thu, Oct 04, 2018 at 07:43:43AM CEST, vasundhara-v.volam@broadcom.com wrote:
>>This patchset adds support for 3 generic and 1 driver-specific devlink
>>parameters. Add documentation for these configuration parameters.
>>
>>Also, this patchset adds support to return proper error code if
>>HWRM_NVM_GET/SET_VARIABLE commands return error code
>>HWRM_ERR_CODE_RESOURCE_ACCESS_DENIED.
>>
>>v3->v4:
>>-Remove extra definition of NVM_OFF_HW_TC_OFFLOAD from bnxt_devlink.h
>>-Remove type information for generic parameters from
>>devlink-params-bnxt.txt
>>
>>v2->v3:
>>-Remove description of generic parameters from devlink-params-bnxt.txt
>>
>>v1->v2:
>>-Remove hw_tc_offload parameter.
>>-Update all patches with Cc of MAINTAINERS.
>>-Add more description in commit message for device specific parameter.
>>-Add a new Documentation/networking/devlink-params.txt with some
>>generic devlink parameters information.
>>-Add a new Documentation/networking/devlink-params-bnxt.txt with devlink
>>parameters information that are supported by bnxt_en driver.
>>
>>Vasundhara Volam (9):
>> devlink: Add generic parameter ignore_ari
>> devlink: Add generic parameter msix_vec_per_pf_max
>> devlink: Add generic parameter msix_vec_per_pf_min
>> bnxt_en: Use ignore_ari devlink parameter
>> bnxt_en: return proper error when FW returns
>> HWRM_ERR_CODE_RESOURCE_ACCESS_DENIED
>> bnxt_en: Use msix_vec_per_pf_max and msix_vec_per_pf_min devlink
>> params.
>> bnxt_en: Add a driver specific gre_ver_check devlink parameter.
>> devlink: Add Documentation/networking/devlink-params.txt
>> devlink: Add Documentation/networking/devlink-params-bnxt.txt
>
> Looks good to me. For the whole set:
> Acked-by: Jiri Pirko <jiri@mellanox.com>
Series applied, thanks.
prev parent reply other threads:[~2018-10-05 3:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 5:43 [PATCH v4 net-next 0/9] bnxt_en: devlink param updates Vasundhara Volam
2018-10-04 5:43 ` [PATCH v4 net-next 1/9] devlink: Add generic parameter ignore_ari Vasundhara Volam
2018-10-04 5:43 ` [PATCH v4 net-next 2/9] devlink: Add generic parameter msix_vec_per_pf_max Vasundhara Volam
2018-10-04 5:43 ` [PATCH v4 net-next 3/9] devlink: Add generic parameter msix_vec_per_pf_min Vasundhara Volam
2018-10-04 5:43 ` [PATCH v4 net-next 4/9] bnxt_en: Use ignore_ari devlink parameter Vasundhara Volam
2018-10-04 5:43 ` [PATCH v4 net-next 5/9] bnxt_en: return proper error when FW returns HWRM_ERR_CODE_RESOURCE_ACCESS_DENIED Vasundhara Volam
2018-10-04 5:43 ` [PATCH v4 net-next 6/9] bnxt_en: Use msix_vec_per_pf_max and msix_vec_per_pf_min devlink params Vasundhara Volam
2018-10-04 5:43 ` [PATCH v4 net-next 7/9] bnxt_en: Add a driver specific gre_ver_check devlink parameter Vasundhara Volam
2018-10-04 5:43 ` [PATCH v4 net-next 8/9] devlink: Add Documentation/networking/devlink-params.txt Vasundhara Volam
2018-10-09 6:21 ` Saeed Mahameed
2018-10-09 6:47 ` Vasundhara Volam
2018-10-04 5:43 ` [PATCH v4 net-next 9/9] devlink: Add Documentation/networking/devlink-params-bnxt.txt Vasundhara Volam
2018-10-04 10:39 ` [PATCH v4 net-next 0/9] bnxt_en: devlink param updates Jiri Pirko
2018-10-04 20:50 ` David Miller [this message]
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=20181004.135021.719953370786213619.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gerlitz.or@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=jiri@mellanox.com \
--cc=jiri@resnulli.us \
--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