public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Angelo Dureghello <angelo70@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Baruch Siach <baruch@tkos.co.il>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-m68k@vger.kernel.org,
	uClinux development list <uclinux-dev@uclinux.org>
Subject: Re: dm9000 patch
Date: Wed, 29 Dec 2010 13:16:32 -0800	[thread overview]
Message-ID: <1293657392.31071.15.camel@Joe-Laptop> (raw)
In-Reply-To: <4D1BA0D0.1060407@gmail.com>

On Wed, 2010-12-29 at 21:57 +0100, Angelo Dureghello wrote:
> the kernel is a main line kernel. Then yes, i am still using uclinux 
> tree for libc/tools.

Does it still occur if you remove the debug line below?
---
 drivers/net/dm9000.c |    2 --
 1 files changed, 0 insertions(+), 2 deletions(-)

diff --git a/drivers/net/dm9000.c b/drivers/net/dm9000.c
index 2d4c4fc..c774430 100644
--- a/drivers/net/dm9000.c
+++ b/drivers/net/dm9000.c
@@ -1077,8 +1077,6 @@ static irqreturn_t dm9000_interrupt(int irq, void *dev_id)
 	unsigned long flags;
 	u8 reg_save;
 
-	dm9000_dbg(db, 3, "entering %s\n", __func__);
-
 	/* A real interrupt coming */
 
 	/* holders of db->lock must always block IRQs */



  reply	other threads:[~2010-12-29 21:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4D1A5C2A.5050606@gmail.com>
2010-12-29  6:06 ` dm9000 patch Baruch Siach
2010-12-29  8:48   ` Angelo Dureghello
2010-12-29 13:13   ` Angelo Dureghello
2010-12-29 18:06     ` Baruch Siach
2010-12-29 18:45       ` Geert Uytterhoeven
2010-12-29 20:57         ` Angelo Dureghello
2010-12-29 21:16           ` Joe Perches [this message]
2010-12-30  0:37           ` Greg Ungerer
2010-12-30  9:53             ` Angelo Dureghello
2010-12-30  9:59             ` Angelo Dureghello
2010-12-30 11:17               ` Greg Ungerer
2010-12-30 15:05                 ` [uClinux-dev] " Angelo Dureghello
2010-12-30 15:12                   ` Baruch Siach

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=1293657392.31071.15.camel@Joe-Laptop \
    --to=joe@perches.com \
    --cc=angelo70@gmail.com \
    --cc=baruch@tkos.co.il \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=uclinux-dev@uclinux.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