From: Roman Kurakin <rik@cronyx.ru>
To: linux-kernel@vger.kernel.org
Subject: Serial.c BUG 2.4.x-2.5x
Date: Fri, 01 Mar 2002 15:18:38 +0300 [thread overview]
Message-ID: <3C7F719E.3040402@cronyx.ru> (raw)
Hi,
Who is responsible person for applying patches to main tree?
This time I decide to send 2.5.5 patch version:
--- serial-255.c Thu Feb 28 19:24:47 2002
+++ ../serial-255.c Wed Feb 20 05:10:59 2002
@@ -2084,7 +2084,6 @@
unsigned int i,change_irq,change_port;
int retval = 0;
unsigned long new_port;
- unsigned long new_mem;
if (copy_from_user(&new_serial,new_info,sizeof(new_serial)))
return -EFAULT;
@@ -2094,7 +2093,6 @@
new_port = new_serial.port;
if (HIGH_BITS_OFFSET)
new_port += (unsigned long) new_serial.port_high <<
HIGH_BITS_OFFSET;
- new_mem = new_serial.iomem_base;
change_irq = new_serial.irq != state->irq;
change_port = (new_port != ((int) state->port)) ||
@@ -2136,7 +2134,6 @@
for (i = 0 ; i < NR_PORTS; i++)
if ((state != &rs_table[i]) &&
(rs_table[i].port == new_port) &&
- (rs_table[i].iomem_base == new_mem) &&
rs_table[i].type)
return -EADDRINUSE;
}
-------- Original Message --------
Subject: Serial.c Bug
Date: Wed, 14 Nov 2001 13:02:47 +0300
From: Roman Kurakin <rik@cronyx.ru>
To: linux-kernel@vger.kernel.org
I have found a bug. It is in support of serial cards which uses
memory for
I/O insted of ports. I made a patch for serial.c and fix one place, but
probably the problem like this one could be somewhere else.
If you try to use setserial with such cards you will get "Address in use"
(-EADDRINUSE)
Best regards,
Kurakin Roman
Best regards,
Roman Kurakin
next reply other threads:[~2002-03-01 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 12:18 Roman Kurakin [this message]
2002-03-01 19:07 Serial.c BUG 2.4.x-2.5x Ed Vance
2002-03-06 20:39 ` Russell King
2002-03-07 13:53 ` Roman Kurakin
2002-03-07 16:51 Ed Vance
2002-03-19 0:16 Ed Vance
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=3C7F719E.3040402@cronyx.ru \
--to=rik@cronyx.ru \
--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;
as well as URLs for NNTP newsgroup(s).