All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Cc: john.ronciak@intel.com, ganesh.venkatesan@intel.com,
	jesse.brandeburg@intel.com, jgarzik@pobox.com,
	Jon_Wetzel@Dell.com
Subject: [patch 2.6.13 7/16] e100: support ETHTOOL_GPERMADDR
Date: Mon, 12 Sep 2005 10:48:56 -0400	[thread overview]
Message-ID: <09122005104856.32157@bilbo.tuxdriver.com> (raw)
In-Reply-To: <09122005104855.32092@bilbo.tuxdriver.com>

Add support for ETHTOOL_GPERMADDR to e100.

Signed-off-by: John W. Linville <linville@tuxdriver.com>
---

 drivers/net/e100.c |    4 +++-
 1 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/drivers/net/e100.c b/drivers/net/e100.c
--- a/drivers/net/e100.c
+++ b/drivers/net/e100.c
@@ -2391,6 +2391,7 @@ static struct ethtool_ops e100_ethtool_o
 	.phys_id		= e100_phys_id,
 	.get_stats_count	= e100_get_stats_count,
 	.get_ethtool_stats	= e100_get_ethtool_stats,
+	.get_perm_addr		= ethtool_op_get_perm_addr,
 };
 
 static int e100_do_ioctl(struct net_device *netdev, struct ifreq *ifr, int cmd)
@@ -2541,7 +2542,8 @@ static int __devinit e100_probe(struct p
 	e100_phy_init(nic);
 
 	memcpy(netdev->dev_addr, nic->eeprom, ETH_ALEN);
-	if(!is_valid_ether_addr(netdev->dev_addr)) {
+	memcpy(netdev->perm_addr, nic->eeprom, ETH_ALEN);
+	if(!is_valid_ether_addr(netdev->perm_addr)) {
 		DPRINTK(PROBE, ERR, "Invalid MAC address from "
 			"EEPROM, aborting.\n");
 		err = -EAGAIN;

  reply	other threads:[~2005-09-12 15:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-12 14:48 [patch 2.6.13 0/16] implement ETHTOOL_GPERMADDR support for a number of drivers John W. Linville
2005-09-12 14:48 ` [patch 2.6.13 1/16] 3c59x: support ETHTOOL_GPERMADDR John W. Linville
2005-09-12 14:48   ` [patch 2.6.13 2/16] 8139cp: " John W. Linville
2005-09-12 14:48     ` [patch 2.6.13 3/16] 8139too: " John W. Linville
2005-09-12 14:48       ` [patch 2.6.13 4/16] b44: " John W. Linville
2005-09-12 14:48         ` [patch 2.6.13 5/16] bnx2: " John W. Linville
2005-09-12 14:48           ` [patch 2.6.13 6/16] e1000: " John W. Linville
2005-09-12 14:48             ` John W. Linville [this message]
2005-09-12 14:48               ` [patch 2.6.13 8/16] forcedeth: " John W. Linville
2005-09-12 14:48                 ` [patch 2.6.13 9/16] ixgb: " John W. Linville
2005-09-12 14:48                   ` [patch 2.6.13 10/16] ne2k-pci: " John W. Linville
2005-09-12 14:48                     ` [patch 2.6.13 11/16] pcnet32: " John W. Linville
2005-09-12 14:48                       ` [patch 2.6.13 12/16] r8169: " John W. Linville
2005-09-12 14:48                         ` [patch 2.6.13 13/16] skge: " John W. Linville
2005-09-12 14:48                           ` [patch 2.6.13 14/16] sundance: " John W. Linville
2005-09-12 14:48                             ` [patch 2.6.13 15/16] tg3: " John W. Linville
2005-09-12 14:48                               ` [patch 2.6.13 16/16] via-rhine: " John W. Linville

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=09122005104856.32157@bilbo.tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=Jon_Wetzel@Dell.com \
    --cc=ganesh.venkatesan@intel.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=jgarzik@pobox.com \
    --cc=john.ronciak@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.