Spelling fixes for relevent -> relevant in 15 files.

diff -ur linux-2.5-current/arch/v850/kernel/ma.c linux/arch/v850/kernel/ma.c
@@ -61,7 +61,7 @@
 	   specific chips may have more).  */
 	if (chan < 2) {
 		unsigned bits = 0x3 << (chan * 3);
-		/* Specify that the relevent pins on the chip should do
+		/* Specify that the relevant pins on the chip should do
 		   serial I/O, not direct I/O.  */
 		MA_PORT4_PMC |= bits;
 		/* Specify that we're using the UART, not the CSI device.  */

diff -ur linux-2.5-current/arch/v850/kernel/rte_ma1_cb.c linux/arch/v850/kernel/rte_ma1_cb.c
@@ -93,7 +93,7 @@
 		/* Turn on the timer.  */
 		NB85E_TIMER_C_TMCC0 (tc) |= NB85E_TIMER_C_TMCC0_CAE;
 
-	/* Make sure the relevent port0/port1 pins are assigned
+	/* Make sure the relevant port0/port1 pins are assigned
 	   interrupt duty.  We used INTP001-INTP011 (don't screw with
 	   INTP000 because the monitor uses it).  */
 	MA_PORT0_PMC |= 0x4;	/* P02 (INTP001) in IRQ mode.  */

diff -ur linux-2.5-current/drivers/acpi/hardware/hwregs.c linux/drivers/acpi/hardware/hwregs.c
@@ -370,7 +370,7 @@
 
 		/*
 		 * Status Registers are different from the rest.  Clear by
-		 * writing 1, writing 0 has no effect.  So, the only relevent
+		 * writing 1, writing 0 has no effect.  So, the only relevant
 		 * information is the single bit we're interested in, all others should
 		 * be written as 0 so they will be left unchanged
 		 */

diff -ur linux-2.5-current/drivers/char/rio/list.h linux/drivers/char/rio/list.h
@@ -111,7 +111,7 @@
 /*
 ** can_remove_receive( PacketP, PortP ) returns non-zero if PKT_IN_USE is set
 ** for the next packet on the queue. It will also set PacketP to point to the
-** relevent packet, [having cleared the PKT_IN_USE bit]. If PKT_IN_USE is clear,
+** relevant packet, [having cleared the PKT_IN_USE bit]. If PKT_IN_USE is clear,
 ** then can_remove_receive() returns 0.
 */
 #if defined(MIPS) || defined(nx6000) || defined(drs6000) || defined(UWsparc)

diff -ur linux-2.5-current/drivers/char/rio/rioparam.c linux/drivers/char/rio/rioparam.c
@@ -714,7 +714,7 @@
 /*
 ** can_remove_receive(PktP,P) returns non-zero if PKT_IN_USE is set
 ** for the next packet on the queue. It will also set PktP to point to the
-** relevent packet, [having cleared the PKT_IN_USE bit]. If PKT_IN_USE is clear,
+** relevant packet, [having cleared the PKT_IN_USE bit]. If PKT_IN_USE is clear,
 ** then can_remove_receive() returns 0.
 */
 int

diff -ur linux-2.5-current/drivers/char/rio/rioroute.c linux/drivers/char/rio/rioroute.c
@@ -521,7 +521,7 @@
       /*
       ** If either of the modules on this unit is read-only or write-only
       ** or none-xprint, then we need to transfer that info over to the
-      ** relevent ports.
+      ** relevant ports.
       */
       if ( HostP->Mapping[ThisUnit].SysPort != NO_PORT )
       {

diff -ur linux-2.5-current/drivers/i2c/i2c-algo-ibm_ocp.c linux/drivers/i2c/i2c-algo-ibm_ocp.c
@@ -758,7 +758,7 @@
         // Check to see if the bus is busy
         //
         ret = iic_inb(adap, iic->extsts);
-        // Mask off the irrelevent bits
+        // Mask off the irrelevant bits
         ret = ret & 0x70;
         // When the bus is free, the BCS bits in the EXTSTS register are 0b100
         if(ret != 0x40) return IIC_ERR_LOST_ARB;

diff -ur linux-2.5-current/drivers/isdn/hisax/rawhdlc.c linux/drivers/isdn/hisax/rawhdlc.c
@@ -34,7 +34,7 @@
  * end-of-frame would occur), so the transmitter performs
  * "bit-stuffing" - inserting a zero bit after every five one bits,
  * irregardless of the original bit after the five ones.  Byte
- * ordering is irrelevent at this point - the data is treated as a
+ * ordering is irrelevant at this point - the data is treated as a
  * string of bits, not bytes.  Since no more than 5 ones may now occur
  * in a row, the flag sequence, with its 6 ones, is unique.
  *

diff -ur linux-2.5-current/drivers/serial/sa1100.c linux/drivers/serial/sa1100.c
@@ -327,7 +327,7 @@
 			sa1100_rx_chars(sport, regs);
 		}
 
-		/* Clear the relevent break bits */
+		/* Clear the relevant break bits */
 		if (status & (UTSR0_RBB | UTSR0_REB))
 			UART_PUT_UTSR0(sport, status & (UTSR0_RBB | UTSR0_REB));
 

diff -ur linux-2.5-current/fs/adfs/dir_f.c linux/fs/adfs/dir_f.c
@@ -259,7 +259,7 @@
 
 /*
  * get a directory entry.  Note that the caller is responsible
- * for holding the relevent locks.
+ * for holding the relevant locks.
  */
 int
 __adfs_dir_get(struct adfs_dir *dir, int pos, struct object_info *obj)

diff -ur linux-2.5-current/fs/afs/vnode.c linux/fs/afs/vnode.c
@@ -272,7 +272,7 @@
 /*****************************************************************************/
 /*
  * break any outstanding callback on a vnode
- * - only relevent to server that issued it
+ * - only relevant to server that issued it
  */
 int afs_vnode_give_up_callback(afs_vnode_t *vnode)
 {

diff -ur linux-2.5-current/kernel/futex.c linux/kernel/futex.c
@@ -39,7 +39,7 @@
 
 /*
  * We use this hashed waitqueue instead of a normal wait_queue_t, so
- * we can wake only the relevent ones (hashed queues may be shared):
+ * we can wake only the relevant ones (hashed queues may be shared):
  */
 struct futex_q {
 	struct list_head list;