From: Jeff Garzik <jeff@garzik.org>
To: Dhananjay Phadke <dhananjay@netxen.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 6/7] netxen: add module parameters
Date: Thu, 14 Aug 2008 04:46:24 -0400 [thread overview]
Message-ID: <48A3F0E0.6060006@garzik.org> (raw)
In-Reply-To: <1218179325-32493-7-git-send-email-dhananjay@netxen.com>
Dhananjay Phadke wrote:
> Add user tunable params to enable/disable msi/msix, port auto-neg modes.
>
> Signed-off-by: Dhananjay Phadke <dhananjay@netxen.com>
> ---
> drivers/net/netxen/netxen_nic_main.c | 10 +++++++++-
> 1 files changed, 9 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/net/netxen/netxen_nic_main.c b/drivers/net/netxen/netxen_nic_main.c
> index 3c424a8..ee56511 100644
> --- a/drivers/net/netxen/netxen_nic_main.c
> +++ b/drivers/net/netxen/netxen_nic_main.c
> @@ -50,13 +50,21 @@ static char netxen_nic_driver_string[] = "NetXen Network Driver version "
> NETXEN_NIC_LINUX_VERSIONID;
>
> static int port_mode = NETXEN_PORT_MODE_AUTO_NEG;
> +module_param(port_mode, int, 0);
> +MODULE_PARM_DESC(port_mode, "Force port mode Auto-Neg XG, 1G or XG");
>
> /* Default to restricted 1G auto-neg mode */
> -static int wol_port_mode = 5;
> +static int wol_port_mode = NETXEN_PORT_MODE_AUTO_NEG_1G;
> +module_param(wol_port_mode, int, 0);
> +MODULE_PARM_DESC(wol_port_mode, "Force WOL port mode XG, 1G or Auto-Neg");
>
> static int use_msi = 1;
> +module_param(use_msi, bool, 0);
> +MODULE_PARM_DESC(use_msi, "Enable or disable MSI interrupts");
>
> static int use_msi_x = 1;
> +module_param(use_msi_x, bool, 0);
> +MODULE_PARM_DESC(use_msi_x, "Enable or disable MSI-X interrupts");
typically it is preferred not add module parameters for each type of
setting. drivers should auto-configure themselves, modulo PCI quirks
and the like.
prev parent reply other threads:[~2008-08-14 8:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 7:08 [PATCH 6/7] netxen: add module parameters Dhananjay Phadke
2008-08-14 8:46 ` Jeff Garzik [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=48A3F0E0.6060006@garzik.org \
--to=jeff@garzik.org \
--cc=dhananjay@netxen.com \
--cc=netdev@vger.kernel.org \
/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).