From: David Miller <davem@davemloft.net>
To: felix.manlunas@cavium.com
Cc: netdev@vger.kernel.org, raghu.vatsavayi@cavium.com,
derek.chickles@cavium.com, satananda.burla@cavium.com,
intiyaz.basha@cavium.com
Subject: Re: [PATCH V2 net-next 0/6] liquidio: enhanced ethtool --set-channels feature
Date: Mon, 30 Apr 2018 09:26:53 -0400 (EDT) [thread overview]
Message-ID: <20180430.092653.1474854564188442801.davem@davemloft.net> (raw)
In-Reply-To: <20180428063204.GA3229@felix-thinkpad.cavium.com>
From: Felix Manlunas <felix.manlunas@cavium.com>
Date: Fri, 27 Apr 2018 23:32:04 -0700
> From: Intiyaz Basha <intiyaz.basha@cavium.com>
>
> For the ethtool --set-channels feature, the liquidio driver currently
> accepts max combined value as the queue count configured during driver
> load time, where max combined count is the total count of input and output
> queues. This limitation is applicable only when SR-IOV is enabled, that
> is, when VFs are created for PF. If SR-IOV is not enabled, the driver can
> configure max supported (64) queues.
>
> This series of patches are for enhancing driver to accept
> max supported queues for ethtool --set-channels.
>
> Changes in V2:
> Only patch #6 was changed to fix these Sparse warnings reported by kbuild
> test robot:
> lio_ethtool.c:848:5: warning: symbol 'lio_23xx_reconfigure_queue_count'
> was not declared. Should it be static?
> lio_ethtool.c:877:22: warning: incorrect type in assignment (different
> base types)
> lio_ethtool.c:878:22: warning: incorrect type in assignment (different
> base types)
> lio_ethtool.c:879:22: warning: incorrect type in assignment (different
> base types)
Series applied, thank you.
prev parent reply other threads:[~2018-04-30 13:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 6:32 [PATCH V2 net-next 0/6] liquidio: enhanced ethtool --set-channels feature Felix Manlunas
2018-04-28 6:32 ` [PATCH V2 net-next 1/6] liquidio: Moved common function if_cfg_callback to lio_core.c Felix Manlunas
2018-04-28 6:32 ` [PATCH V2 net-next 2/6] liquidio: Moved common function list_delete_head to octeon_network.h Felix Manlunas
2018-04-28 6:32 ` [PATCH V2 net-next 3/6] liquidio: Moved common function delete_glists to lio_core.c Felix Manlunas
2018-04-28 6:32 ` [PATCH V2 net-next 4/6] liquidio: Moved common definition octnic_gather to octeon_network.h Felix Manlunas
2018-04-28 6:32 ` [PATCH V2 net-next 5/6] liquidio: Moved common function setup_glists to lio_core.c Felix Manlunas
2018-04-28 6:32 ` [PATCH V2 net-next 6/6] liquidio: enhanced ethtool --set-channels feature Felix Manlunas
2018-04-30 13:26 ` 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=20180430.092653.1474854564188442801.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=derek.chickles@cavium.com \
--cc=felix.manlunas@cavium.com \
--cc=intiyaz.basha@cavium.com \
--cc=netdev@vger.kernel.org \
--cc=raghu.vatsavayi@cavium.com \
--cc=satananda.burla@cavium.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).