All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@grandegger.com>
To: netdev@vger.kernel.org
Cc: socketcan-core@lists.berlios.de, Wolfgang Grandegger <wg@grandegger.com>
Subject: [net-next-2.6 PATCH 1/3] can: some fixes and cleanups to the initial device driver interface
Date: Sat, 30 May 2009 19:55:48 +0200	[thread overview]
Message-ID: <20090530175547.973220489@denx.de> (raw)
In-Reply-To: 20090530175547.772116783@denx.de

[-- Attachment #1: misc-fixes.patch --]
[-- Type: text/plain, Size: 2114 bytes --]

This patch fixes a few errors sneaked into the initial version of the
device driver interface.

Signed-off-by: Wolfgang Grandegger <wg@grandegger.com>
---
 drivers/net/can/dev.c             |    2 +-
 drivers/net/can/sja1000/ems_pci.c |    3 ---
 drivers/net/can/sja1000/sja1000.c |    2 +-
 3 files changed, 2 insertions(+), 5 deletions(-)

Index: net-next-2.6/drivers/net/can/dev.c
===================================================================
--- net-next-2.6.orig/drivers/net/can/dev.c	2009-05-30 19:48:32.820720048 +0200
+++ net-next-2.6/drivers/net/can/dev.c	2009-05-30 19:48:38.044719620 +0200
@@ -477,7 +477,7 @@
 
 	return 0;
 }
-EXPORT_SYMBOL(open_candev);
+EXPORT_SYMBOL_GPL(open_candev);
 
 /*
  * Common close function for cleanup before the device gets closed.
Index: net-next-2.6/drivers/net/can/sja1000/ems_pci.c
===================================================================
--- net-next-2.6.orig/drivers/net/can/sja1000/ems_pci.c	2009-05-30 19:48:32.821720749 +0200
+++ net-next-2.6/drivers/net/can/sja1000/ems_pci.c	2009-05-30 19:48:38.045719203 +0200
@@ -218,14 +218,12 @@
 	card->conf_addr = pci_iomap(pdev, 0, EMS_PCI_MEM_SIZE);
 	if (card->conf_addr == NULL) {
 		err = -ENOMEM;
-
 		goto failure_cleanup;
 	}
 
 	card->base_addr = pci_iomap(pdev, 1, EMS_PCI_MEM_SIZE);
 	if (card->base_addr == NULL) {
 		err = -ENOMEM;
-
 		goto failure_cleanup;
 	}
 
@@ -239,7 +237,6 @@
 	    ems_pci_readb(card, 3) != 0xCB ||
 	    ems_pci_readb(card, 4) != 0x11) {
 		dev_err(&pdev->dev, "Not EMS Dr. Thomas Wuensche interface\n");
-
 		err = -ENODEV;
 		goto failure_cleanup;
 	}
Index: net-next-2.6/drivers/net/can/sja1000/sja1000.c
===================================================================
--- net-next-2.6.orig/drivers/net/can/sja1000/sja1000.c	2009-05-30 19:48:32.821720749 +0200
+++ net-next-2.6/drivers/net/can/sja1000/sja1000.c	2009-05-30 19:48:38.057718952 +0200
@@ -532,8 +532,8 @@
 		err = request_irq(dev->irq, &sja1000_interrupt, priv->irq_flags,
 				  dev->name, (void *)dev);
 		if (err) {
-			return -EAGAIN;
 			close_candev(dev);
+			return -EAGAIN;
 		}
 	}
 


  reply	other threads:[~2009-05-30 17:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-30 17:55 [net-next-2.6 PATCH 0/3] can: sja1000: misused netdev->base_addr and OF platform driver Wolfgang Grandegger
2009-05-30 17:55 ` Wolfgang Grandegger [this message]
2009-05-30 17:55 ` [net-next-2.6 PATCH 2/3] can: sja1000: stop misusing member base_addr of struct net_device Wolfgang Grandegger
2009-05-30 17:55 ` [net-next-2.6 PATCH 3/3] can: sja1000: generic OF platform bus driver Wolfgang Grandegger
2009-06-01  9:54 ` [net-next-2.6 PATCH 0/3] can: sja1000: misused netdev->base_addr and OF platform driver 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=20090530175547.973220489@denx.de \
    --to=wg@grandegger.com \
    --cc=netdev@vger.kernel.org \
    --cc=socketcan-core@lists.berlios.de \
    /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.