From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linus Torvalds <torvalds@transmeta.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [PATCH] Mac/m68k sonic updates
Date: Sat, 26 Jul 2003 16:51:38 +0200 [thread overview]
Message-ID: <200307261451.h6QEpcR1002292@callisto.of.borg> (raw)
Mac/m68k sonic: Kill warning and remainings of 2.2-style flow control
--- linux-2.6.x/drivers/net/macsonic.c Mon Aug 5 12:48:53 2002
+++ linux-m68k-2.6.x/drivers/net/macsonic.c Fri Jun 6 12:22:46 2003
@@ -142,7 +142,7 @@
int __init macsonic_init(struct net_device* dev)
{
- struct sonic_local* lp;
+ struct sonic_local* lp = NULL;
int i;
/* Allocate the entire chunk of memory for the descriptors.
--- linux-2.6.x/drivers/net/sonic.c Fri Mar 1 11:05:29 2002
+++ linux-m68k-2.6.x/drivers/net/sonic.c Mon Sep 16 14:41:46 2002
@@ -113,15 +113,6 @@
if (sonic_debug > 2)
printk("sonic_send_packet: skb=%p, dev=%p\n", skb, dev);
- /*
- * Block a timer-based transmit from overlapping. This could better be
- * done with atomic_swap(1, dev->tbusy), but set_bit() works as well.
- */
- if (test_and_set_bit(0, (void *) &dev->tbusy) != 0) {
- printk("%s: Transmitter access conflict.\n", dev->name);
- return 1;
- }
-
/*
* Map the packet data into the logical DMA address space
*/
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2003-07-26 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-26 14:51 Geert Uytterhoeven [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-15 19:10 [PATCH] Mac/m68k sonic updates Geert Uytterhoeven
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=200307261451.h6QEpcR1002292@callisto.of.borg \
--to=geert@linux-m68k.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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).