linux-kernel - [PATCH 1/4] arch/xtensa: Use UPIO_MEM rather than SERIAL_IO

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Wed, 5 Aug 2009 15:23:08 +0200 (CEST)
From:	Julia Lawall <julia@...u.dk>
To:	Chris Zankel <chris@...kel.net>, linux-kernel@...r.kernel.org,
	kernel-janitors@...r.kernel.org
Subject: [PATCH 1/4] arch/xtensa: Use UPIO_MEM rather than SERIAL_IO_MEM

From: Julia Lawall <julia@...u.dk>

As in the commit 9b4a1617772d6d5ab5eeda0cd95302fae119e359, use UPIO_MEM
rather than SERIAL_IO_MEM.  Both have the same value.

The semantic patch that makes this change is as follows:
(http://coccinelle.lip6.fr/)

// <smpl>
@has_sc@
@@

#include <linux/serial_core.h>

@depends on has_sc@
@@

- SERIAL_IO_MEM
+ UPIO_MEM
// </smpl>

Signed-off-by: Julia Lawall <julia@...u.dk>

---
 arch/xtensa/platforms/s6105/device.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff -u -p a/arch/xtensa/platforms/s6105/device.c b/arch/xtensa/platforms/s6105/device.c
--- a/arch/xtensa/platforms/s6105/device.c
+++ b/arch/xtensa/platforms/s6105/device.c
@@ -54,7 +54,7 @@ static struct plat_serial8250_port seria
 		.irq = UART_INTNUM,
 		.uartclk = S6_SCLK,
 		.regshift = 2,
-		.iotype = SERIAL_IO_MEM,
+		.iotype = UPIO_MEM,
 		.flags = ASYNC_BOOT_AUTOCONF | ASYNC_SKIP_TEST,
 	},
 	{
@@ -63,7 +63,7 @@ static struct plat_serial8250_port seria
 		.irq = UART_INTNUM,
 		.uartclk = S6_SCLK,
 		.regshift = 2,
-		.iotype = SERIAL_IO_MEM,
+		.iotype = UPIO_MEM,
 		.flags = ASYNC_BOOT_AUTOCONF | ASYNC_SKIP_TEST,
 	},
 	{ },
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/