From Klaus-D. Wacker <kdwacker@de.ibm.com>

Signed-off-by: Klaus-D. Wacker <kdwacker@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
---

 Documentation/kmsg/s390/lcs |  170 ++++++++++++++++++++++++++++++++++++++++++++
 drivers/s390/net/lcs.c      |   78 +++++++++++---------
 2 files changed, 216 insertions(+), 32 deletions(-)

Index: kmsg-2.6/Documentation/kmsg/s390/lcs
===================================================================
--- /dev/null
+++ kmsg-2.6/Documentation/kmsg/s390/lcs
@@ -0,0 +1,170 @@
+/*?
+ * Tag: lcs.1666ed
+ * Text: "%s:  Allocating a socket buffer to interface %s failed\n"
+ * Severity: Error
+ * Parameter:
+ *   @1: bus ID of the LCS device
+ *   @2: network interface
+ * Description:
+ * LAN channel station (LCS) devices require a socket buffer (SKB) structure
+ * for storing incoming data. The LCS device driver failed to allocate an SKB
+ * structure to the LCS device. A likely cause of this problem is memory
+ * constraints.
+ * User action:
+ * Free some memory and repeat the failed operation.
+ */
+
+/*?
+ * Tag: lcs.fd3431
+ * Text: "%s:  Shutting down the LCS device failed\n "
+ * Severity: Error
+ * Parameter:
+ *   @1: bus ID of the LCS device
+ * Description:
+ * A request to shut down a LAN channel station (LCS) device resulted in an
+ * error. The error is logged in the LCS trace at trace level 4.
+ * User action:
+ * Try again to shut down the device. If the error persists, see the LCS trace
+ * to find out what causes the error.
+ */
+
+/*?
+ * Tag: lcs.c4ca7a
+ * Text: "%s: Detecting a network adapter for LCS devices failed with rc=%d (0x%x)\n"
+ * Severity: Error
+ * Parameter:
+ *   @1: lcs_detect return code in decimal notation
+ *   @2: lcs_detect return code in hexadecimal notation
+ * Description:
+ * The LCS device driver could not initialize a network adapter.
+ * User action:
+ * Note the return codes from the error message and contact IBM support.
+ */
+
+/*?
+ * Tag: ...
[ message continues ]

Hello Mr. Martin schwidefsky,
   I expect your patch will be merged into the kernel tree soon.
   My friends and I have been working for providing a kernel
   message online manual called "OSS Message Pedia" (mPedia) in
   Japan.
   I’d like to introduce mPedia briefly here because the kprintk
   patch will affect our mPedia activities in Japan.

   Development of OSS Message Pedia was partly supported by IPA
   (Information-Technology Promotion Agency) Japan and it has
   been opened to the public.
   mPedia has internationalization function inside but currently
   it has only Japanese contents except some sample English contents.
   For example, you can find English contents with the following URL:

      http://ossmpedia.org/messages/linux/2.6.9-34.EL/297.en

   (You can change the tag 'languages' to "ja" to get Japanese
    contents.)

   Also you can find some English documentation about mPedia by
   visiting the following URL:

       http://ossmpedia.wiki.sourceforge.net/

   We hope we could have some contribution to the kernel messaging
   with the mPedia activities in Japan. Though we don't have a
   particular solution about how to tie-up the kernel messaging at
   this moment, we think some difficulties in the mPedia maintenance
   and enhancements could be reduced with the kprintk patch.

   (1) We have about 850 kernel message explanation contents in
       Japanese. The each content includes meaning, actions, etc.

   (2) We're now considering how to translate Japanese contents
       into English. (No bright idea came yet.)

   We appreciate your efforts for improving kernel messaging and
   the patch integration.

   (I added "server-messagedb-tf@ipa.go.jp" in CC.)

   Thank you.

Best Regards,
Hideki Takahashi
--

[ message continues ]