Changed the path from to the incorrect drivers/char/sysrq.c to drivers/tty/sysrq.c

This is my first patch submission. Please let me know if I have made a mistake anywhere.

---
 Documentation/sysrq.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

index 13f5619..3a3b30a 100644
@@ -212,7 +212,7 @@ it is currently registered in that slot. This is in case the slot has been
 overwritten since you registered it.
 
 The Magic SysRQ system works by registering key operations against a 

key op
-lookup table, which is defined in 'drivers/char/sysrq.c'. This key table has +lookup table, which is defined in 'drivers/tty/sysrq.c'. This key table has
a number of operations registered into it at compile time, but is mutable, and 2 functions are exported for interface to it:
register_sysrq_key and unregister_sysrq_key.

2.8.0

Thank you for improving the documentation!

Unfortunately, the patch was corrupted by your mail client and does not apply. Could I please ask you to have a look at Documentation/email-clients.txt for information on how to send patches so that they arrive intact at the other end? A good approach is to email the patch to yourself and ensure that the result applies before trying again.

Thanks,

jon

Jonathan

You're right, the lines were wrapped at character 78. I have fixed that and sent the patch to myself. The attached patch should work now.

René

---
 Documentation/sysrq.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

index 13f5619..3a3b30a 100644
@@ -212,7 +212,7 @@ it is currently registered in that slot. This is in case the slot has been
 overwritten since you registered it.
 
 The Magic SysRQ system works by registering key operations against a key op
-lookup table, which is defined in 'drivers/char/sysrq.c'. This key table has
+lookup table, which is defined in 'drivers/tty/sysrq.c'. This key table has
 a number of operations registered into it at compile time, but is mutable,
 and 2 functions are exported for interface to it:
 	register_sysrq_key and unregister_sysrq_key.

2.8.0

The patch applies, but the above text is not a proper commit message, so I still can't apply it without editing it. I've done that this time around, but, in the future, please be sure that the entire patch posting is suitable for application.

Thanks,

jon