netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: <jie.yang@atheros.com>
Cc: <jeff@garzik.org>, <yjwei@cn.fujitsu.com>, <rdreier@cisco.com>,
	<davem@davemloft.net>, <jcliburn@gmail.com>,
	<parag.warudkar@gmail.com>, <w@1wt.eu>,
	<oliver.schuster@schweigstill.de>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next] atl1e: Atheros L1E Gigabit Ethernet driver
Date: Thu, 17 Jul 2008 08:44:50 -0700	[thread overview]
Message-ID: <20080717084450.42ceca96@extreme> (raw)
In-Reply-To: <12162854952457-git-send-email-jie.yang@atheros.com>


> +/*
> + * atl1e_check_options - Range Checking for Command Line Parameters
> + * @adapter: board private structure
> + *
> + * This routine checks all command line parameters for valid user
> + * input.  If an invalid value is given, or if no user specified
> + * value exists, a default value is used.  The final value is stored
> + * in a variable in the adapter structure.
> + */
> +void __devinit atl1e_check_options(struct atl1e_adapter *adapter)
> +{
> +	struct pci_dev *pdev = adapter->pdev;
> +	int bd = adapter->bd_number;
> +	if (bd >= ATL1E_MAX_NIC) {
> +		dev_notice(&pdev->dev, "no configuration for board #%i\n", bd);
> +		dev_notice(&pdev->dev, "Using defaults for all values\n");
> +	}


The use of module parameters to set options is discouraged, especially
when there are better choices. All these parameter should be controllable by ethtool.
The reason is that users (and tools) shouldn't have to know the
special parameters that are specific to that hardware.

This version is okay as is for initial inclusion, but the parameters should
be removed later.

  parent reply	other threads:[~2008-07-17 15:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17  9:04 [PATCH net-next] atl1e: Atheros L1E Gigabit Ethernet driver jie.yang
2008-07-17  9:31 ` Alexey Dobriyan
2008-07-17  9:41   ` Jie Yang
2008-07-17 15:44 ` Stephen Hemminger [this message]
2008-07-17 20:04 ` Mariusz Kozlowski
2008-07-17 20:23   ` Ben Hutchings
2008-07-17 21:37   ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2008-07-18  3:37 jie.yang
2008-07-22 23:31 ` Jeff Garzik
2008-07-14  3:28 Jie Yang
2008-07-16  4:15 ` Stephen Hemminger
2008-07-16  9:42   ` Jie Yang
2008-07-16 15:53     ` Stephen Hemminger
2008-07-16 16:36       ` Roland Dreier
2008-07-17  2:47         ` Jie Yang
2008-07-17  3:30           ` Wei Yongjun
2008-07-17  3:34             ` Stephen Hemminger

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=20080717084450.42ceca96@extreme \
    --to=shemminger@vyatta.com \
    --cc=davem@davemloft.net \
    --cc=jcliburn@gmail.com \
    --cc=jeff@garzik.org \
    --cc=jie.yang@atheros.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oliver.schuster@schweigstill.de \
    --cc=parag.warudkar@gmail.com \
    --cc=rdreier@cisco.com \
    --cc=w@1wt.eu \
    --cc=yjwei@cn.fujitsu.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).