From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: PATCH: rio driver rework continued #5
Date: Wed, 15 Mar 2006 12:31:55 +0000 [thread overview]
Message-ID: <1142425915.5597.21.camel@localhost.localdomain> (raw)
Final polish. There is no more save_flags/cli type locking left. We also
no longer use the pcicopy function and file so they can go.
Signed-off-by: Alan Cox <alan@redhat.com>
diff -u --new-file --recursive --exclude-from /usr/src/exclude linux.vanilla-2.6.16-rc6-mm1/drivers/char/Kconfig linux-2.6.16-rc6-mm1/drivers/char/Kconfig
--- linux.vanilla-2.6.16-rc6-mm1/drivers/char/Kconfig 2006-03-14 13:00:22.000000000 +0000
+++ linux-2.6.16-rc6-mm1/drivers/char/Kconfig 2006-03-14 14:48:08.000000000 +0000
@@ -290,7 +290,7 @@
config RIO
tristate "Specialix RIO system support"
- depends on SERIAL_NONSTANDARD && BROKEN_ON_SMP && !64BIT
+ depends on SERIAL_NONSTANDARD && !64BIT
help
This is a driver for the Specialix RIO, a smart serial card which
drives an outboard box that can support up to 128 ports. Product
diff -u --new-file --recursive --exclude-from /usr/src/exclude linux.vanilla-2.6.16-rc6-mm1/drivers/char/rio/Makefile linux-2.6.16-rc6-mm1/drivers/char/rio/Makefile
--- linux.vanilla-2.6.16-rc6-mm1/drivers/char/rio/Makefile 2006-03-14 12:59:37.000000000 +0000
+++ linux-2.6.16-rc6-mm1/drivers/char/rio/Makefile 2006-03-14 17:20:30.000000000 +0000
@@ -9,4 +9,4 @@
obj-$(CONFIG_RIO) += rio.o
rio-objs := rio_linux.o rioinit.o rioboot.o riocmd.o rioctrl.o riointr.o \
- rioparam.o riopcicopy.o rioroute.o riotable.o riotty.o
+ rioparam.o rioroute.o riotable.o riotty.o
diff -u --new-file --recursive --exclude-from /usr/src/exclude linux.vanilla-2.6.16-rc6-mm1/drivers/char/rio/riopcicopy.c linux-2.6.16-rc6-mm1/drivers/char/rio/riopcicopy.c
--- linux.vanilla-2.6.16-rc6-mm1/drivers/char/rio/riopcicopy.c 2006-03-14 12:59:37.000000000 +0000
+++ linux-2.6.16-rc6-mm1/drivers/char/rio/riopcicopy.c 1970-01-01 01:00:00.000000000 +0100
@@ -1,8 +0,0 @@
-
-/* Yeah. We have copyright on this one. Sure. */
-
-void rio_pcicopy(char *from, char *to, int amount)
-{
- while (amount--)
- *to++ = *from++;
-}
reply other threads:[~2006-03-15 12:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1142425915.5597.21.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®