linux.git/drivers/serial/serial_core.c, branch v2.6.13 Linux kernel source tree [PATCH] Serial: Fix console port spinlock initialisation 2005-07-03T20:05:45+00:00 Russell King rmk@dyn-67.arm.linux.org.uk 2005-07-03T20:05:45+00:00 976ecd12b8144d066a23fe97c6fbfc1ac8470af7 Initialise the spinlock for port being used by the console early, but don't re-initialise it again later. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 
Initialise the spinlock for port being used by the console early, but
don't re-initialise it again later.

Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
[PATCH] Serial: Check status of CTS when using flow control 2005-06-29T17:40:53+00:00 Russell King rmk@dyn-67.arm.linux.org.uk 2005-06-29T17:40:53+00:00 0dd7a1aed7c34a39917c4faf75b4230c169e809b Fix bugme #4712: read the CTS status and set hw_stopped if CTS is not active when opening the port and/or enabling CRTSCTS Thanks to Stefan Wolff for spotting this problem. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 
Fix bugme #4712: read the CTS status and set hw_stopped if CTS
is not active when opening the port and/or enabling CRTSCTS

Thanks to Stefan Wolff for spotting this problem.

Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
[PATCH] Serial: Adjust serial locking 2005-06-29T08:42:38+00:00 Russell King rmk@dyn-67.arm.linux.org.uk 2005-06-29T08:42:38+00:00 c5f4644e6c8ba21666128603e4e92544d3cd740d This patch changes the way serial ports are locked when getting modem status. This change is necessary because we will need to atomically read the modem status and take action depending on the CTS status. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 
This patch changes the way serial ports are locked when getting modem
status.  This change is necessary because we will need to atomically
read the modem status and take action depending on the CTS status.

Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Linux-2.6.12-rc2 2005-04-16T22:20:36+00:00 Linus Torvalds torvalds@ppc970.osdl.org 2005-04-16T22:20:36+00:00 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip! 
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.

Let it rip!