From: Alexander Beregalov <a.beregalov@gmail.com>
To: netdev@vger.kernel.org
Subject: [PATCH 10/11] ioc3-eth: convert to net_device_ops
Date: Sat, 11 Apr 2009 21:44:55 +0400 [thread overview]
Message-ID: <20090411174455.GJ16999@orion> (raw)
In-Reply-To: <20090411173019.GA16999@orion>
Signed-off-by: Alexander Beregalov <a.beregalov@gmail.com>
---
drivers/net/ioc3-eth.c | 22 ++++++++++++++--------
1 files changed, 14 insertions(+), 8 deletions(-)
diff --git a/drivers/net/ioc3-eth.c b/drivers/net/ioc3-eth.c
index cbc63ff..c5593f4 100644
--- a/drivers/net/ioc3-eth.c
+++ b/drivers/net/ioc3-eth.c
@@ -1214,6 +1214,19 @@ static void __devinit ioc3_serial_probe(struct pci_dev *pdev, struct ioc3 *ioc3)
}
#endif
+static const struct net_device_ops ioc3_netdev_ops = {
+ .ndo_open = ioc3_open,
+ .ndo_stop = ioc3_close,
+ .ndo_start_xmit = ioc3_start_xmit,
+ .ndo_tx_timeout = ioc3_timeout,
+ .ndo_get_stats = ioc3_get_stats,
+ .ndo_set_multicast_list = ioc3_set_multicast_list,
+ .ndo_do_ioctl = ioc3_ioctl,
+ .ndo_validate_addr = eth_validate_addr,
+ .ndo_set_mac_address = ioc3_set_mac_address,
+ .ndo_change_mtu = eth_change_mtu,
+};
+
static int __devinit ioc3_probe(struct pci_dev *pdev,
const struct pci_device_id *ent)
{
@@ -1310,15 +1323,8 @@ static int __devinit ioc3_probe(struct pci_dev *pdev,
ioc3_get_eaddr(ip);
/* The IOC3-specific entries in the device structure. */
- dev->open = ioc3_open;
- dev->hard_start_xmit = ioc3_start_xmit;
- dev->tx_timeout = ioc3_timeout;
dev->watchdog_timeo = 5 * HZ;
- dev->stop = ioc3_close;
- dev->get_stats = ioc3_get_stats;
- dev->do_ioctl = ioc3_ioctl;
- dev->set_multicast_list = ioc3_set_multicast_list;
- dev->set_mac_address = ioc3_set_mac_address;
+ dev->netdev_ops = &ioc3_netdev_ops;
dev->ethtool_ops = &ioc3_ethtool_ops;
dev->features = NETIF_F_IP_CSUM;
next prev parent reply other threads:[~2009-04-11 17:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-11 17:30 [PATCH 01/11] xtsonic: convert to net_device_ops Alexander Beregalov
2009-04-11 17:37 ` [PATCH 02/11] tsi108_eth: " Alexander Beregalov
2009-04-13 22:19 ` David Miller
2009-04-11 17:38 ` [PATCH 03/11] tc35815: " Alexander Beregalov
2009-04-13 22:19 ` David Miller
2009-04-11 17:39 ` [PATCH 04/11] sun3_82586: " Alexander Beregalov
2009-04-13 22:19 ` David Miller
2009-04-11 17:40 ` [PATCH 05/11] sh_eth: " Alexander Beregalov
2009-04-13 22:19 ` David Miller
2009-04-11 17:41 ` [PATCH 06/11] macsonic: " Alexander Beregalov
2009-04-13 22:19 ` David Miller
2009-04-11 17:42 ` [PATCH 07/11] macb: " Alexander Beregalov
2009-04-13 22:19 ` David Miller
2009-04-11 17:43 ` [PATCH 08/11] mac89x0: " Alexander Beregalov
2009-04-13 22:19 ` David Miller
2009-04-11 17:44 ` [PATCH 09/11] isa-skeleton: " Alexander Beregalov
2009-04-13 22:19 ` David Miller
2009-04-11 17:44 ` Alexander Beregalov [this message]
2009-04-13 22:19 ` [PATCH 10/11] ioc3-eth: " David Miller
2009-04-11 17:45 ` [PATCH 11/11] eth_v10: " Alexander Beregalov
2009-04-13 22:20 ` David Miller
2009-04-13 22:19 ` [PATCH 01/11] xtsonic: " David Miller
2009-04-13 23:12 ` Alexander Beregalov
2009-04-13 23:19 ` David Miller
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=20090411174455.GJ16999@orion \
--to=a.beregalov@gmail.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).