From: David Miller <davem@davemloft.net>
To: amit.salecha@qlogic.com
Cc: netdev@vger.kernel.org, ameen.rahman@qlogic.com,
anirban.chakraborty@qlogic.com
Subject: Re: [PATCH NEXT 1/2] qlcnic: fix type of module parameters
Date: Tue, 22 Feb 2011 10:31:47 -0800 (PST) [thread overview]
Message-ID: <20110222.103147.28828271.davem@davemloft.net> (raw)
In-Reply-To: <1298289514-15671-2-git-send-email-amit.salecha@qlogic.com>
From: Amit Kumar Salecha <amit.salecha@qlogic.com>
Date: Mon, 21 Feb 2011 03:58:33 -0800
> o Module parameters auto_fw_reset, use_msi, use_msi_x, qlcnic_mac_learn,
> and load_fw_file should be of type bool not int.
> o All module parameters should have qlcnic prefix.
> o Remove unnecessary macro for value "1".
>
> Signed-off-by: Amit Kumar Salecha <amit.salecha@qlogic.com>
You must not change module parameter names on a whim, as this will
break scripts.
When you create a module parameter in your driver, you are creating
something users will use, and therefore an API. You therefore
cannot change it without breaking stuff.
This is yet another reason I scream at anyone who adds module
parameters to network drivers, they are always "the wrong thing
to do".
None of these values you guys have module parameter for in the
qlcnic driver are providing facilities that are really qlcnic
specific at all.
MSI-X enablement, firmware loading controls, etc. All of this
stuff is generic and would be potentially necessary in any device
driver, not just qlcnic's.
Therefore generic facilities are where this stuff should be
implemented, instead of in driver specific module parameters.
I will not apply these patches, sorry.
next prev parent reply other threads:[~2011-02-22 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 11:58 [PATCH NEXT 0/2]qlcnic: minor fixes Amit Kumar Salecha
2011-02-21 11:58 ` [PATCH NEXT 1/2] qlcnic: fix type of module parameters Amit Kumar Salecha
2011-02-22 18:31 ` David Miller [this message]
2011-02-21 11:58 ` [PATCH NEXT 2/2] qlcnic: Remove validation for max tx and max rx queues Amit Kumar Salecha
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=20110222.103147.28828271.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ameen.rahman@qlogic.com \
--cc=amit.salecha@qlogic.com \
--cc=anirban.chakraborty@qlogic.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).