[PATCH 051/199] Documentation/isdn/HiSax.cert: Checkpatch cleanup

[PATCH 051/199] Documentation/isdn/HiSax.cert: Checkpatch cleanup

[Andrea Gelmini]

Documentation/isdn/HiSax.cert:26: ERROR: trailing whitespace
Documentation/isdn/HiSax.cert:31: ERROR: trailing whitespace
Documentation/isdn/HiSax.cert:32: ERROR: trailing whitespace
Documentation/isdn/HiSax.cert:35: ERROR: trailing whitespace
Documentation/isdn/HiSax.cert:36: ERROR: trailing whitespace
Documentation/isdn/HiSax.cert:38: ERROR: trailing whitespace

Signed-off-by: Andrea Gelmini <andrea.gelmini@gelma.net>
---
 Documentation/isdn/HiSax.cert |   12 ++++++------
 1 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/Documentation/isdn/HiSax.cert b/Documentation/isdn/HiSax.cert
index f2a6fcb..26ab655 100644
--- a/Documentation/isdn/HiSax.cert
+++ b/Documentation/isdn/HiSax.cert
@@ -23,19 +23,19 @@ therefore affect the certification.
 Additional ITU approval tests have been carried out for all generic cards
 using Colognechip single chip solutions HFC-S PCI A for PCI cards as well
 as HFC-S USB based USB ISDN ta adapters.
-These tests included all layers 1-3 and as well all functional tests for 
+These tests included all layers 1-3 and as well all functional tests for
 the layer 1. Because all hardware based on these chips are complete ISDN
 solutions in one chip all cards and USB-TAs using these chips are to be
 regarded as approved for those tests. Some additional electrical tests
 of the layer 1 which are independent of the driver and related to a
-special hardware used will be regarded as approved if at least one 
-solution has been tested including those electrical tests. So if cards 
+special hardware used will be regarded as approved if at least one
+solution has been tested including those electrical tests. So if cards
 or tas have been completely approved for any other os, the approval
 for those electrical tests is valid for linux, too.
-Please send any questions regarding this drivers or approval abouts to 
-werner@isdn-development.de 
+Please send any questions regarding this drivers or approval abouts to
+werner@isdn-development.de
 Additional information and the type approval documents will be found
-shortly on the Colognechip website www.colognechip.com 
+shortly on the Colognechip website www.colognechip.com
 
 If you change the main files of the HiSax ISDN stack, the certification will
 become invalid. Because in most countries it is illegal to connect
-- 
1.7.1.251.gf80a2

[PATCH 052/199] Documentation/isdn/INTERFACE: Checkpatch cleanup

[Andrea Gelmini]

Documentation/isdn/INTERFACE:39: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:40: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:56: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:74: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:123: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:135: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:239: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:243: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:253: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:415: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:423: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:426: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:434: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:437: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:440: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:461: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:462: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:524: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:526: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:530: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:535: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:537: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:579: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:609: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:667: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:697: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:715: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:716: ERROR: trailing whitespace
Documentation/isdn/INTERFACE:726: ERROR: trailing whitespace

Signed-off-by: Andrea Gelmini <andrea.gelmini@gelma.net>
---
 Documentation/isdn/INTERFACE |   58 +++++++++++++++++++++---------------------
 1 files changed, 29 insertions(+), 29 deletions(-)

diff --git a/Documentation/isdn/INTERFACE b/Documentation/isdn/INTERFACE
index 5df17e5..5054867 100644
--- a/Documentation/isdn/INTERFACE
+++ b/Documentation/isdn/INTERFACE
@@ -36,8 +36,8 @@ Description of the Interface between Linklevel and Hardwarelevel
   Changes in this document are marked with '***CHANGEx' where x representing
   the version number. If that number starts with 0, it refers to the old,
   separately distributed package. If it starts with one of the letters
-  above, it refers to the revision of the corresponding module. 
-  ***CHANGEIx refers to the revision number of the isdnif.h  
+  above, it refers to the revision of the corresponding module.
+  ***CHANGEIx refers to the revision number of the isdnif.h
 
 1. Description of the fields of isdn_if:
 
@@ -53,7 +53,7 @@ Description of the Interface between Linklevel and Hardwarelevel
     ***CHANGE0.6: New since this version.
 
     Also to be preset by the HL-driver. With this value the HL-driver
-    tells the LL the maximum size of a data-packet it will accept. 
+    tells the LL the maximum size of a data-packet it will accept.
 
   unsigned long features;
 
@@ -71,7 +71,7 @@ Description of the Interface between Linklevel and Hardwarelevel
 
     To be preset by the HL-driver, if it supports sk_buff's. The driver
     should put here the amount of additional space needed in sk_buff's for
-    its internal purposes. Drivers not supporting sk_buff's should 
+    its internal purposes. Drivers not supporting sk_buff's should
     initialize this field to 0.
 
   void (*rcvcallb_skb)(int, int, struct sk_buff *)
@@ -120,7 +120,7 @@ Description of the Interface between Linklevel and Hardwarelevel
         command = command to perform. (one of the constants ISDN_CMD_...)
         arg     = depends on command.
         num     = depends on command.
-    
+
     Returnvalue:
       >=0 on success, else error-code (-ENODEV etc.)
 
@@ -132,7 +132,7 @@ Description of the Interface between Linklevel and Hardwarelevel
     This field has to be preset by the HL-driver. The given function will
     be called by the LL for delivering data to be send via B-Channel.
 
- 
+
     Parameter:
       int              driver-Id ***CHANGE0.7.4: New parameter.
       int              channel-number locally to the HL-driver. (starts with 0)
@@ -236,11 +236,11 @@ Description of the Interface between Linklevel and Hardwarelevel
        command  = ISDN_CMD_IOCTL
        arg      = Original ioctl-cmd - IIOCDRVCTL
        parm.num = first bytes filled with (unsigned long)arg
-   
+
      Returnvalue:
        Depending on driver.
 
-  
+
   ISDN_CMD_DIAL:
 
     This command is used to tell the HL-driver it should dial a given
@@ -250,7 +250,7 @@ Description of the Interface between Linklevel and Hardwarelevel
       driver      = driver-Id.
       command     = ISDN_CMD_DIAL
       arg         = channel-number locally to the driver. (starting with 0)
-      
+
       parm.setup.phone  = An ASCII-String containing the number to dial.
       parm.setup.eazmsn = An ASCII-Sting containing the own EAZ or MSN.
       parm.setup.si1    = The Service-Indicator.
@@ -412,7 +412,7 @@ Description of the Interface between Linklevel and Hardwarelevel
     Returnvalue:
       current protocol-Id (one of the constants ISDN_L3_PROTO)
 
-  ISDN_CMD_PROCEED: 
+  ISDN_CMD_PROCEED:
 
     With this command, the HL-driver is told to proceed with a incoming call.
 
@@ -420,10 +420,10 @@ Description of the Interface between Linklevel and Hardwarelevel
       driver      = driver-Id.
       command     = ISDN_CMD_PROCEED
       arg         = channel-number locally to the driver. (starting with 0)
-      setup.eazmsn= empty string or string send as uus1 in DSS1 with 
+      setup.eazmsn= empty string or string send as uus1 in DSS1 with
                     PROCEED message
 
-  ISDN_CMD_ALERT: 
+  ISDN_CMD_ALERT:
 
     With this command, the HL-driver is told to alert a proceeding call.
 
@@ -431,13 +431,13 @@ Description of the Interface between Linklevel and Hardwarelevel
       driver      = driver-Id.
       command     = ISDN_CMD_ALERT
       arg         = channel-number locally to the driver. (starting with 0)
-      setup.eazmsn= empty string or string send as uus1 in DSS1 with 
+      setup.eazmsn= empty string or string send as uus1 in DSS1 with
                     ALERT message
 
-  ISDN_CMD_REDIR: 
+  ISDN_CMD_REDIR:
 
     With this command, the HL-driver is told to redirect a call in proceeding
-    or alerting state.  
+    or alerting state.
 
     Parameter:
       driver      = driver-Id.
@@ -458,8 +458,8 @@ Description of the Interface between Linklevel and Hardwarelevel
       command     = ISDN_CMD_PROT_IO
       arg         = The lower 8 Bits define the addressed protocol as defined
                     in ISDN_PTYPE..., the upper bits are used to differentiate
-                    the protocol specific CMD.  
-      
+                    the protocol specific CMD.
+
       para        = protocol and function specific. See isdnif.h for detail.
 
 
@@ -521,20 +521,20 @@ Description of the Interface between Linklevel and Hardwarelevel
                     HL-driver may send ALERTING on the D-channel in this case.
       2           = Call will be rejected.
       3           = Incoming called party number is currently incomplete.
-                    Additional digits are required. 
+                    Additional digits are required.
                     Used for signalling with PtP connections.
-      4	          = Call will be held in a proceeding state 
+      4	          = Call will be held in a proceeding state
                     (HL driver sends PROCEEDING)
                     Used when a user space prog needs time to interpret a call
 		    para.setup.eazmsn may be filled with an uus1 message of
-		    30 octets maximum. Empty string if no uus. 
+		    30 octets maximum. Empty string if no uus.
       5           = Call will be actively deflected to another party
                     Only available in DSS1/EURO protocol
 		    para.setup.phone must be set to destination party number
 		    para.setup.eazmsn may be filled with an uus1 message of
-		    30 octets maximum. Empty string if no uus. 
+		    30 octets maximum. Empty string if no uus.
       -1          = An error happened. (Invalid parameters for example.)
-  The keypad support now is included in the dial command.	        
+  The keypad support now is included in the dial command.
 
 
   ISDN_STAT_RUN:
@@ -576,7 +576,7 @@ Description of the Interface between Linklevel and Hardwarelevel
    a B-Channel-connection. (Response to ISDN_CMD_ACCEPTB or because the
    remote-station has initiated establishment)
 
-   The HL driver should call this when the logical l2/l3 protocol 
+   The HL driver should call this when the logical l2/l3 protocol
    connection on top of the physical B-channel is established.
 
     Parameter:
@@ -606,7 +606,7 @@ Description of the Interface between Linklevel and Hardwarelevel
    B-Channel-connection. This could be a response to a prior ISDN_CMD_HANGUP,
    or caused by a remote-hangup.
 
-   The HL driver should call this as soon as the logical l2/l3 protocol 
+   The HL driver should call this as soon as the logical l2/l3 protocol
    connection on top of the physical B-channel is released.
 
     Parameter:
@@ -664,7 +664,7 @@ Description of the Interface between Linklevel and Hardwarelevel
       arg         = channel-number, locally to the driver. (starting with 0)
       parm        = unused.
 
-  ISDN_STAT_ADDCH: 
+  ISDN_STAT_ADDCH:
 
     This call is for HL-drivers, which are unable to check card-type
     or numbers of supported channels before they have loaded any firmware
@@ -694,7 +694,7 @@ Description of the Interface between Linklevel and Hardwarelevel
   ISDN_STAT_DISPLAY:
 
     With this call, the HL-driver delivers DISPLAY-messages to the LL.
-    Currently the LL does not use this messages. 
+    Currently the LL does not use this messages.
 
     Parameter:
       driver      = driver-Id
@@ -712,8 +712,8 @@ Description of the Interface between Linklevel and Hardwarelevel
       command     = ISDN_STAT_PROT
       arg         = The lower 8 Bits define the addressed protocol as defined
                     in ISDN_PTYPE..., the upper bits are used to differentiate
-                    the protocol specific STAT.  
-      
+                    the protocol specific STAT.
+
       para        = protocol and function specific. See isdnif.h for detail.
 
   ISDN_STAT_DISCH:
@@ -723,7 +723,7 @@ Description of the Interface between Linklevel and Hardwarelevel
     The call may be used to reduce the available number of B-channels after
     loading the driver. The LL has to ignore a disabled channel when searching
     for free channels. The HL driver itself never delivers STAT callbacks for
-    disabled channels. 	    
+    disabled channels.
     The LL returns a nonzero code if the operation was not successful or the
     selected channel is actually regarded as busy.
 
-- 
1.7.1.251.gf80a2

[PATCH 053/199] Documentation/isdn/README.HiSax: Checkpatch cleanup

[Andrea Gelmini]

Documentation/isdn/README.HiSax:62: ERROR: trailing whitespace
Documentation/isdn/README.HiSax:191: ERROR: trailing whitespace
Documentation/isdn/README.HiSax:192: ERROR: trailing whitespace
Documentation/isdn/README.HiSax:200: ERROR: trailing whitespace

Signed-off-by: Andrea Gelmini <andrea.gelmini@gelma.net>
---
 Documentation/isdn/README.HiSax |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/Documentation/isdn/README.HiSax b/Documentation/isdn/README.HiSax
index 031c8d8..de8a9fc 100644
--- a/Documentation/isdn/README.HiSax
+++ b/Documentation/isdn/README.HiSax
@@ -59,7 +59,7 @@ Traverse Technologie NETjet PCI S0 card and NETspider U card
 Ovislink ISDN sc100-p card (NETjet driver)
 Dr. Neuhaus Niccy PnP/PCI
 Siemens I-Surf 1.0
-Siemens I-Surf 2.0 (with IPAC, try type 12 asuscom) 
+Siemens I-Surf 2.0 (with IPAC, try type 12 asuscom)
 ACER P10
 HST Saphir
 Berkom Telekom A4T
@@ -188,8 +188,8 @@ Card types:
    27   AVM PnP (Fritz!PnP)      irq, io  (from isapnp setup)
    27   AVM PCI (Fritz!PCI)      no parameter
    28   Sedlbauer Speed Fax+     irq, io (from isapnp setup)
-   29	Siemens I-Surf 1.0       irq, io, memory (from isapnp setup)   
-   30	ACER P10                 irq, io (from isapnp setup)   
+   29	Siemens I-Surf 1.0       irq, io, memory (from isapnp setup)
+   30	ACER P10                 irq, io (from isapnp setup)
    31	HST Saphir               irq, io
    32	Telekom A4T              none
    33	Scitel Quadro		 subcontroller (4*S0, subctrl 1...4)
@@ -197,7 +197,7 @@ Card types:
    34	Gazel ISDN cards (PCI)   none
    35	HFC 2BDS0 PCI            none
    36	W6692 based PCI cards    none
-   37	HFC 2BDS0 S+, SP         irq,io 
+   37	HFC 2BDS0 S+, SP         irq,io
    38	NETspider U PCI card     none
    39	HFC 2BDS0 SP/PCMCIA      irq,io (set with cardmgr)
    40   hotplug interface
-- 
1.7.1.251.gf80a2

[PATCH 054/199] Documentation/isdn/README.act2000: Checkpatch cleanup

[Andrea Gelmini]

Documentation/isdn/README.act2000:19: ERROR: trailing whitespace
Documentation/isdn/README.act2000:20: ERROR: trailing whitespace
Documentation/isdn/README.act2000:21: ERROR: trailing whitespace
Documentation/isdn/README.act2000:22: ERROR: trailing whitespace
Documentation/isdn/README.act2000:23: ERROR: trailing whitespace
Documentation/isdn/README.act2000:24: ERROR: trailing whitespace
Documentation/isdn/README.act2000:26: ERROR: trailing whitespace
Documentation/isdn/README.act2000:27: ERROR: trailing whitespace
Documentation/isdn/README.act2000:28: ERROR: trailing whitespace
Documentation/isdn/README.act2000:29: ERROR: trailing whitespace
Documentation/isdn/README.act2000:30: ERROR: trailing whitespace
Documentation/isdn/README.act2000:31: ERROR: trailing whitespace
Documentation/isdn/README.act2000:32: ERROR: trailing whitespace
Documentation/isdn/README.act2000:64: ERROR: trailing whitespace

Signed-off-by: Andrea Gelmini <andrea.gelmini@gelma.net>
---
 Documentation/isdn/README.act2000 |   28 ++++++++++++++--------------
 1 files changed, 14 insertions(+), 14 deletions(-)

diff --git a/Documentation/isdn/README.act2000 b/Documentation/isdn/README.act2000
index ce7115e..dcc61b2 100644
--- a/Documentation/isdn/README.act2000
+++ b/Documentation/isdn/README.act2000
@@ -16,20 +16,20 @@ Setting up the DIP switches for the IBM Active 2000 ISDN card:
 
      S1  S2  S3  S4  Base-port
      on  on  on  on  0x0200 (Factory default)
-     off on  on  on  0x0240 
-     on  off on  on  0x0280 
-     off off on  on  0x02c0 
-     on  on  off on  0x0300 
-     off on  off on  0x0340 
-     on  off off on  0x0380 
+     off on  on  on  0x0240
+     on  off on  on  0x0280
+     off off on  on  0x02c0
+     on  on  off on  0x0300
+     off on  off on  0x0340
+     on  off off on  0x0380
      on  on  on  off 0xcfe0
-     off on  on  off 0xcfa0 
-     on  off on  off 0xcf60 
-     off off on  off 0xcf20 
-     on  on  off off 0xcee0 
-     off on  off off 0xcea0 
-     on  off off off 0xce60 
-     off off off off Card disabled 
+     off on  on  off 0xcfa0
+     on  off on  off 0xcf60
+     off off on  off 0xcf20
+     on  on  off off 0xcee0
+     off on  off off 0xcea0
+     on  off off off 0xce60
+     off off off off Card disabled
 
 IRQ is configured by software. Possible values are:
 
@@ -61,7 +61,7 @@ Driver built into the kernel:
 
   which means: Autoprobe for an ISA card, use next free IRQ, let the
   ISDN linklevel fill the IdString (usually "line0" for the first card).
- 
+
   If you like to use more than one card, you can use the program
   "actctrl" from the utility-package to configure additional cards.
 
-- 
1.7.1.251.gf80a2

[PATCH 055/199] Documentation/isdn/README.audio: Checkpatch cleanup

[Andrea Gelmini]

Documentation/isdn/README.audio:90: ERROR: trailing whitespace

Signed-off-by: Andrea Gelmini <andrea.gelmini@gelma.net>
---
 Documentation/isdn/README.audio |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/Documentation/isdn/README.audio b/Documentation/isdn/README.audio
index 8ebca19..a861f86 100644
--- a/Documentation/isdn/README.audio
+++ b/Documentation/isdn/README.audio
@@ -87,7 +87,7 @@ General behavior and description of data formats/protocol.
       On incoming calls, if the application responds to a RING
       with ATA, depending on the calling service, the emulator
       responds with either CONNECT (data call) or VCON (voice call).
-      
+
       On outgoing voice calls, the emulator responds with VCON
       upon connection setup.
 
-- 
1.7.1.251.gf80a2

[PATCH 056/199] Documentation/isdn/README.avmb1: Checkpatch cleanup

[Andrea Gelmini]

Documentation/isdn/README.avmb1:181: ERROR: trailing whitespace
Documentation/isdn/README.avmb1:183: ERROR: trailing whitespace

Signed-off-by: Andrea Gelmini <andrea.gelmini@gelma.net>
---
 Documentation/isdn/README.avmb1 |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/isdn/README.avmb1 b/Documentation/isdn/README.avmb1
index 9e07548..45dad69 100644
--- a/Documentation/isdn/README.avmb1
+++ b/Documentation/isdn/README.avmb1
@@ -178,9 +178,9 @@ in the body.
 German documentation and several scripts can be found at
 ftp://ftp.avm.de/cardware/b1/linux/
 
-Bugs 
+Bugs
 ----
-If you find any please let me know. 
+If you find any please let me know.
 
 Enjoy,
 
-- 
1.7.1.251.gf80a2

[PATCH 057/199] Documentation/isdn/README.diversion: Checkpatch cleanup

[Andrea Gelmini]

Documentation/isdn/README.diversion:2: ERROR: trailing whitespace
Documentation/isdn/README.diversion:3: ERROR: trailing whitespace
Documentation/isdn/README.diversion:4: ERROR: trailing whitespace
Documentation/isdn/README.diversion:5: ERROR: trailing whitespace
Documentation/isdn/README.diversion:28: ERROR: trailing whitespace
Documentation/isdn/README.diversion:33: ERROR: trailing whitespace
Documentation/isdn/README.diversion:34: ERROR: trailing whitespace
Documentation/isdn/README.diversion:37: ERROR: trailing whitespace
Documentation/isdn/README.diversion:39: ERROR: trailing whitespace
Documentation/isdn/README.diversion:41: ERROR: trailing whitespace
Documentation/isdn/README.diversion:44: ERROR: trailing whitespace
Documentation/isdn/README.diversion:45: ERROR: trailing whitespace
Documentation/isdn/README.diversion:46: ERROR: trailing whitespace
Documentation/isdn/README.diversion:47: ERROR: trailing whitespace
Documentation/isdn/README.diversion:50: ERROR: trailing whitespace
Documentation/isdn/README.diversion:51: ERROR: trailing whitespace
Documentation/isdn/README.diversion:60: ERROR: trailing whitespace
Documentation/isdn/README.diversion:64: ERROR: trailing whitespace
Documentation/isdn/README.diversion:70: ERROR: trailing whitespace
Documentation/isdn/README.diversion:71: ERROR: trailing whitespace
Documentation/isdn/README.diversion:74: ERROR: trailing whitespace
Documentation/isdn/README.diversion:76: ERROR: trailing whitespace
Documentation/isdn/README.diversion:80: ERROR: trailing whitespace
Documentation/isdn/README.diversion:82: ERROR: trailing whitespace
Documentation/isdn/README.diversion:89: ERROR: trailing whitespace
Documentation/isdn/README.diversion:91: ERROR: trailing whitespace
Documentation/isdn/README.diversion:92: ERROR: trailing whitespace
Documentation/isdn/README.diversion:95: ERROR: trailing whitespace
Documentation/isdn/README.diversion:96: ERROR: trailing whitespace
Documentation/isdn/README.diversion:104: ERROR: trailing whitespace
Documentation/isdn/README.diversion:105: ERROR: trailing whitespace
Documentation/isdn/README.diversion:111: ERROR: trailing whitespace
Documentation/isdn/README.diversion:114: ERROR: trailing whitespace
Documentation/isdn/README.diversion:116: ERROR: trailing whitespace
Documentation/isdn/README.diversion:117: ERROR: trailing whitespace
Documentation/isdn/README.diversion:118: ERROR: trailing whitespace
Documentation/isdn/README.diversion:120: ERROR: trailing whitespace
Documentation/isdn/README.diversion:122: ERROR: trailing whitespace
Documentation/isdn/README.diversion:125: ERROR: trailing whitespace

Signed-off-by: Andrea Gelmini <andrea.gelmini@gelma.net>
---
 Documentation/isdn/README.diversion |   78 +++++++++++++++++-----------------
 1 files changed, 39 insertions(+), 39 deletions(-)

diff --git a/Documentation/isdn/README.diversion b/Documentation/isdn/README.diversion
index bddcd5f..24b2647 100644
--- a/Documentation/isdn/README.diversion
+++ b/Documentation/isdn/README.diversion
@@ -1,8 +1,8 @@
 The isdn diversion services are a supporting module working together with
-the isdn4linux and the HiSax module for passive cards. 
-Active cards, TAs and cards using a own or other driver than the HiSax 
-module need to be adapted to the HL<->LL interface described in a separate 
-document. The diversion services may be used with all cards supported by 
+the isdn4linux and the HiSax module for passive cards.
+Active cards, TAs and cards using a own or other driver than the HiSax
+module need to be adapted to the HL<->LL interface described in a separate
+document. The diversion services may be used with all cards supported by
 the HiSax driver.
 The diversion kernel interface and controlling tool divertctrl were written
 by Werner Cornelius (werner@isdn4linux.de or werner@titro.de) under the
@@ -25,30 +25,30 @@ GNU General Public License.
 Table of contents
 =================
 
-1. Features of the i4l diversion services 
+1. Features of the i4l diversion services
    (Or what can the i4l diversion services do for me)
 
 2. Required hard- and software
 
-3. Compiling, installing and loading/unloading the module  
-   Tracing calling and diversion information 
+3. Compiling, installing and loading/unloading the module
+   Tracing calling and diversion information
 
 4. Tracing calling and diversion information
- 
+
 5. Format of the divert device ASCII output
- 
 
-1. Features of the i4l diversion services 
+
+1. Features of the i4l diversion services
    (Or what can the i4l diversion services do for me)
 
-   The i4l diversion services offers call forwarding and logging normally 
-   only supported by isdn phones. Incoming calls may be diverted 
-   unconditionally (CFU), when not reachable (CFNR) or on busy condition 
-   (CFB). 
+   The i4l diversion services offers call forwarding and logging normally
+   only supported by isdn phones. Incoming calls may be diverted
+   unconditionally (CFU), when not reachable (CFNR) or on busy condition
+   (CFB).
    The diversions may be invoked statically in the providers exchange
    as normally done by isdn phones. In this case all incoming calls
-   with a special (or all) service identifiers are forwarded if the 
-   forwarding reason is met. Activated static services may also be 
+   with a special (or all) service identifiers are forwarded if the
+   forwarding reason is met. Activated static services may also be
    interrogated (queried).
    The i4l diversion services additionally offers a dynamic version of
    call forwarding which is not preprogrammed inside the providers exchange
@@ -57,43 +57,43 @@ Table of contents
    compared to the mechanism of ipfwadm or ipchains. If a given rule matches
    the checking process is finished and the rule matching will be applied
    to the call.
-   The rules include primary and secondary service identifiers, called 
+   The rules include primary and secondary service identifiers, called
    number and subaddress, callers number and subaddress and whether the rule
    matches to all filtered calls or only those when all B-channel resources
    are exhausted.
-   Actions that may be invoked by a rule are ignore, proceed, reject, 
+   Actions that may be invoked by a rule are ignore, proceed, reject,
    direct divert or delayed divert of a call.
    All incoming calls matching a rule except the ignore rule a reported and
    logged as ASCII via the proc filesystem (/proc/net/isdn/divert). If proceed
    is selected the call will be held in a proceeding state (without ringing)
    for a certain amount of time to let an external program or client decide
-   how to handle the call. 
-            
+   how to handle the call.
+
 
 2. Required hard- and software
-   
+
    For using the i4l diversion services the isdn line must be of a EURO/DSS1
-   type. Additionally the i4l services only work together with the HiSax 
+   type. Additionally the i4l services only work together with the HiSax
    driver for passive isdn cards. All HiSax supported cards may be used for
    the diversion purposes.
    The static diversion services require the provider having static services
-   CFU, CFNR, CFB activated on an MSN-line. The static services may not be 
+   CFU, CFNR, CFB activated on an MSN-line. The static services may not be
    used on a point-to-point connection. Further the static services are only
-   available in some countries (for example germany). Countries requiring the 
+   available in some countries (for example germany). Countries requiring the
    keypad protocol for activating static diversions (like the netherlands) are
    not supported but may use the tty devices for this purpose.
    The dynamic diversion services may be used in all countries if the provider
    enables the feature CF (call forwarding). This should work on both MSN- and
    point-to-point lines.
    To add and delete rules the additional divertctrl program is needed. This
-   program is part of the isdn4kutils package.   
+   program is part of the isdn4kutils package.
 
-3. Compiling, installing and loading/unloading the module  
-   Tracing calling and diversion information 
+3. Compiling, installing and loading/unloading the module
+   Tracing calling and diversion information
 
 
-   To compile the i4l code with diversion support you need to say yes to the 
-   DSS1 diversion services when selecting the i4l options in the kernel 
+   To compile the i4l code with diversion support you need to say yes to the
+   DSS1 diversion services when selecting the i4l options in the kernel
    config (menuconfig or config).
    After having properly activated a make modules and make modules_install all
    required modules will be correctly installed in the needed modules dirs.
@@ -101,27 +101,27 @@ Table of contents
    standard distributions you will have to add a "insmod dss1_divert" after
    having loaded the global isdn module.
    The module can be loaded without any command line parameters.
-   If the module is actually loaded and active may be checked with a 
-   "cat /proc/modules" or "ls /proc/net/isdn/divert". The divert file is 
+   If the module is actually loaded and active may be checked with a
+   "cat /proc/modules" or "ls /proc/net/isdn/divert". The divert file is
    dynamically created by the diversion module and removed when the module is
    unloaded.
 
 
 4. Tracing calling and diversion information
- 
+
    You also may put a "cat /proc/net/isdn/divert" in the background with the
    output redirected to a file. Then all actions of the module are logged.
-   The divert file in the proc system may be opened more than once, so in 
+   The divert file in the proc system may be opened more than once, so in
    conjunction with inetd and a small remote client on other machines inside
-   your network incoming calls and reactions by the module may be shown on 
-   every listening machine. 
-   If a call is reported as proceeding an external program or client may 
+   your network incoming calls and reactions by the module may be shown on
+   every listening machine.
+   If a call is reported as proceeding an external program or client may
    specify during a certain amount of time (normally 4 to 10 seconds) what
-   to do with that call.      
+   to do with that call.
    To unload the module all open files to the device in the proc system must
-   be closed. Otherwise the module (and isdn.o) may not be unloaded. 
+   be closed. Otherwise the module (and isdn.o) may not be unloaded.
 
 5. Format of the divert device ASCII output
- 
+
    To be done later
 
-- 
1.7.1.251.gf80a2

[PATCH 058/199] Documentation/isdn/README.hfc-pci: Checkpatch cleanup

[Andrea Gelmini]

Documentation/isdn/README.hfc-pci:19: ERROR: trailing whitespace
Documentation/isdn/README.hfc-pci:25: ERROR: trailing whitespace
Documentation/isdn/README.hfc-pci:27: ERROR: trailing whitespace
Documentation/isdn/README.hfc-pci:32: ERROR: trailing whitespace
Documentation/isdn/README.hfc-pci:34: ERROR: trailing whitespace
Documentation/isdn/README.hfc-pci:36: ERROR: trailing whitespace

Signed-off-by: Andrea Gelmini <andrea.gelmini@gelma.net>
---
 Documentation/isdn/README.hfc-pci |   12 ++++++------
 1 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/Documentation/isdn/README.hfc-pci b/Documentation/isdn/README.hfc-pci
index e8a4ef0..a61227f 100644
--- a/Documentation/isdn/README.hfc-pci
+++ b/Documentation/isdn/README.hfc-pci
@@ -16,24 +16,24 @@ And then:
 
 hisaxctrl <driver/cardname> 12 1
 
-This enables the echo mode. If Hex logging is activated the isdnctrlx 
+This enables the echo mode. If Hex logging is activated the isdnctrlx
 devices show a output with a line beginning of HEX: for the providers
 exchange and ECHO: for isdn devices sending to the provider.
 
 If more than one HFC-PCI cards are installed, a specific card may be selected
 at the hisax module load command line. Supply the load command with the desired
-IO-address of the desired card. 
+IO-address of the desired card.
 Example:
-There tree cards installed in your machine at IO-base addresses 0xd000, 0xd400 
+There tree cards installed in your machine at IO-base addresses 0xd000, 0xd400
 and 0xdc00
 If you want to use the card at 0xd400 standalone you should supply the insmod
 or depmod with type=35 io=0xd400.
 If you want to use all three cards, but the order needs to be at 0xdc00,0xd400,
-0xd000 you may give the parameters type=35,35,35 io=0xdc00,0xd400,0xd00 
+0xd000 you may give the parameters type=35,35,35 io=0xdc00,0xd400,0xd00
 Then the desired card will be the initialised in the desired order.
-If the io parameter is used the io addresses of all used cards should be 
+If the io parameter is used the io addresses of all used cards should be
 supplied else the parameter is assumed 0 and a auto search for a free card is
-invoked which may not give the wanted result. 
+invoked which may not give the wanted result.
 
 Comments and reports to werner@isdn4linux.de or werner@isdn-development.de
 
-- 
1.7.1.251.gf80a2

[PATCH 059/199] Documentation/isdn/README.pcbit: Checkpatch cleanup

[Andrea Gelmini]

Documentation/isdn/README.pcbit:10: ERROR: trailing whitespace
Documentation/isdn/README.pcbit:39: ERROR: trailing whitespace

Signed-off-by: Andrea Gelmini <andrea.gelmini@gelma.net>
---
 Documentation/isdn/README.pcbit |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/isdn/README.pcbit b/Documentation/isdn/README.pcbit
index 5125002..6fe8f08 100644
--- a/Documentation/isdn/README.pcbit
+++ b/Documentation/isdn/README.pcbit
@@ -7,7 +7,7 @@ developed in cooperation with Portugal Telecom and Inesc.
 The driver interfaces with the standard kernel isdn facilities
 originally developed by Fritz Elfert in the isdn4linux project.
 
-The common versions of the pcbit board require a firmware that is 
+The common versions of the pcbit board require a firmware that is
 distributed (and copyrighted) by the manufacturer. To load this
 firmware you need "pcbitctl" available on the standard isdn4k-utils
 package or in the pcbit package available in:
@@ -36,5 +36,5 @@ mailing list (isdn4linux@listserv.isdn4linux.de) or directly from me.
 
 regards,
   Pedro.
-		
+
 <roque@di.fc.ul.pt>
-- 
1.7.1.251.gf80a2

[PATCH 060/199] Documentation/isdn/README.sc: Checkpatch cleanup

[Andrea Gelmini]

Documentation/isdn/README.sc:3: ERROR: trailing whitespace
Documentation/isdn/README.sc:30: ERROR: trailing whitespace
Documentation/isdn/README.sc:106: ERROR: trailing whitespace
Documentation/isdn/README.sc:120: ERROR: trailing whitespace
Documentation/isdn/README.sc:123: ERROR: trailing whitespace
Documentation/isdn/README.sc:143: ERROR: trailing whitespace
Documentation/isdn/README.sc:162: ERROR: trailing whitespace
Documentation/isdn/README.sc:165: ERROR: trailing whitespace
Documentation/isdn/README.sc:166: ERROR: trailing whitespace
Documentation/isdn/README.sc:168: ERROR: trailing whitespace
Documentation/isdn/README.sc:187: ERROR: trailing whitespace
Documentation/isdn/README.sc:188: ERROR: trailing whitespace
Documentation/isdn/README.sc:189: ERROR: trailing whitespace
Documentation/isdn/README.sc:192: ERROR: trailing whitespace
Documentation/isdn/README.sc:196: ERROR: trailing whitespace
Documentation/isdn/README.sc:201: ERROR: trailing whitespace
Documentation/isdn/README.sc:202: ERROR: trailing whitespace
Documentation/isdn/README.sc:207: ERROR: trailing whitespace
Documentation/isdn/README.sc:212: ERROR: trailing whitespace
Documentation/isdn/README.sc:213: ERROR: trailing whitespace
Documentation/isdn/README.sc:214: ERROR: trailing whitespace
Documentation/isdn/README.sc:215: ERROR: trailing whitespace
Documentation/isdn/README.sc:217: ERROR: trailing whitespace
Documentation/isdn/README.sc:218: ERROR: trailing whitespace
Documentation/isdn/README.sc:219: ERROR: trailing whitespace
Documentation/isdn/README.sc:220: ERROR: trailing whitespace
Documentation/isdn/README.sc:224: ERROR: trailing whitespace
Documentation/isdn/README.sc:230: ERROR: trailing whitespace
Documentation/isdn/README.sc:237: ERROR: trailing whitespace
Documentation/isdn/README.sc:238: ERROR: trailing whitespace
Documentation/isdn/README.sc:239: ERROR: trailing whitespace
Documentation/isdn/README.sc:240: ERROR: trailing whitespace
Documentation/isdn/README.sc:241: ERROR: trailing whitespace
Documentation/isdn/README.sc:244: ERROR: trailing whitespace
Documentation/isdn/README.sc:247: ERROR: trailing whitespace
Documentation/isdn/README.sc:252: ERROR: trailing whitespace
Documentation/isdn/README.sc:255: ERROR: trailing whitespace
Documentation/isdn/README.sc:264: ERROR: trailing whitespace
Documentation/isdn/README.sc:265: ERROR: trailing whitespace
Documentation/isdn/README.sc:268: ERROR: trailing whitespace

Signed-off-by: Andrea Gelmini <andrea.gelmini@gelma.net>
---
 Documentation/isdn/README.sc |   80 +++++++++++++++++++++---------------------
 1 files changed, 40 insertions(+), 40 deletions(-)

diff --git a/Documentation/isdn/README.sc b/Documentation/isdn/README.sc
index 1153cd9..f9641b8 100644
--- a/Documentation/isdn/README.sc
+++ b/Documentation/isdn/README.sc
@@ -1,6 +1,6 @@
 Welcome to Beta Release 2 of the combination ISDN driver for SpellCaster's
 ISA ISDN adapters. Please note this release 2 includes support for the
-DataCommute/BRI and TeleCommute/BRI adapters only and any other use is 
+DataCommute/BRI and TeleCommute/BRI adapters only and any other use is
 guaranteed to fail. If you have a DataCommute/PRI installed in the test
 computer, we recommend removing it as it will be detected but will not
 be usable.  To see what we have done to Beta Release 2, see section 3.
@@ -27,7 +27,7 @@ TABLE OF CONTENTS
 	 1.2 What is different between this driver and previous drivers?
 	 1.3 How do I setup my system with the correct software to use
 	     this driver release?
-	
+
 	2. Basic Operations
 	 2.1 Unpacking and installing the driver
 	 2.2 Read the man pages!!!
@@ -103,7 +103,7 @@ must ensure that the following software is installed, configured and running:
 	- The latest modules package (modules-2.0.0.tar.gz) from
 	  ftp://sunsite.unc.edu/pub/Linux/kernel/modules-2.0.0.tar.gz
 
-	- The ISDN4Linux tools available from 
+	- The ISDN4Linux tools available from
 	  ftp://ftp.franken.de/pub/isdn4linux/v2.0/isdn4k-utils-2.0.tar.gz
 	  This package may fail to compile for you so you can alternatively
 	  get a pre-compiled version from
@@ -117,10 +117,10 @@ must ensure that the following software is installed, configured and running:
 
 	1. As root, create a directory in a convenient place. We suggest
 	   /usr/src/spellcaster.
-	
+
 	2. Unpack the archive with :
 		tar xzf sc-n.nn.tar.gz -C /usr/src/spellcaster
-	
+
 	3. Change directory to /usr/src/spellcaster
 
 	4. Read the README and RELNOTES files.
@@ -140,7 +140,7 @@ you can specify but you shouldn't need to use any unless this doesn't work.
 Make sure the driver loaded and detected all of the adapters by typing
 'dmesg'.
 
-The driver can be configured so that it is loaded upon startup.  To do this, 
+The driver can be configured so that it is loaded upon startup.  To do this,
 edit the file "/etc/modules/'uname -f'/'uname -v'" and insert the driver name
 "sc" into this file.
 
@@ -159,13 +159,13 @@ If you get a message that says 'initialization of sc failed', then the
 driver failed to detect an adapter or failed to find resources needed such
 as a free IRQ line or shared memory segment. If you are sure there are free
 resources available, use the insmod options detailed in sc(4) to override
-the probing function.  
+the probing function.
 
 Upon testing, the following problem was noted, the driver would load without
-problems, but the board would not respond beyond that point.  When a check was 
-done with 'cat /proc/interrupts' the interrupt count for sc was 0.  In the event 
+problems, but the board would not respond beyond that point.  When a check was
+done with 'cat /proc/interrupts' the interrupt count for sc was 0.  In the event
 of this problem, change the BIOS settings so that the interrupts in question are
-reserved for ISA use only.   
+reserved for ISA use only.
 
 
 2.6 How to setup ISDN4Linux with the driver
@@ -184,75 +184,75 @@ A) 10 steps to the establishment of a basic HDLC connection
 -----------------------------------------------------------
 
 - please open the isdn-hdlc file in the examples directory and follow along...
-	
-	This file is a script used to configure a BRI ISDN TA to establish a 
-	basic HDLC connection between its two channels.  Two network 
+
+	This file is a script used to configure a BRI ISDN TA to establish a
+	basic HDLC connection between its two channels.  Two network
 	interfaces are created and two routes added between the channels.
 
-	i)   using the isdnctrl utility, add an interface with "addif" and 
+	i)   using the isdnctrl utility, add an interface with "addif" and
 	     name it "isdn0"
 	ii)  add the outgoing and inbound telephone numbers
 	iii) set the Layer 2 protocol to hdlc
-	iv)  set the eaz of the interface to be the phone number of that 
+	iv)  set the eaz of the interface to be the phone number of that
 	     specific channel
 	v)   to turn the callback features off, set the callback to "off" and
 	     the callback delay (cbdelay) to 0.
 	vi)  the hangup timeout can be set to a specified number of seconds
-	vii) the hangup upon incoming call can be set on or off 
-	viii) use the ifconfig command to bring up the network interface with 
+	vii) the hangup upon incoming call can be set on or off
+	viii) use the ifconfig command to bring up the network interface with
 	      a specific IP address and point to point address
 	ix)  add a route to the IP address through the isdn0 interface
 	x)   a ping should result in the establishment of the connection
 
-	
+
 B) Establishment of a PPP connection
 ------------------------------------
 
 - please open the isdn-ppp file in the examples directory and follow along...
-	
-	This file is a script used to configure a BRI ISDN TA to establish a 
-	PPP connection 	between the two channels.  The file is almost 
-	identical to the HDLC connection example except that the packet 
+
+	This file is a script used to configure a BRI ISDN TA to establish a
+	PPP connection 	between the two channels.  The file is almost
+	identical to the HDLC connection example except that the packet
 	encapsulation type has to be set.
-	
-	use the same procedure as in the HDLC connection from steps i) to 
-	iii) then, after the Layer 2 protocol is set, set the encapsulation 
-	"encap" to syncppp. With this done, the rest of the steps, iv) to x) 
+
+	use the same procedure as in the HDLC connection from steps i) to
+	iii) then, after the Layer 2 protocol is set, set the encapsulation
+	"encap" to syncppp. With this done, the rest of the steps, iv) to x)
 	can be followed from above.
 
 	Then, the ipppd (ippp daemon) must be setup:
-	
+
 	xi)   use the ipppd function found in /sbin/ipppd to set the following:
 	xii)  take out (minus) VJ compression and bsd compression
 	xiii) set the mru size to 2000
 	xiv)  link the two /dev interfaces to the daemon
 
-NOTE:  A "*" in the inbound telephone number specifies that a call can be 
+NOTE:  A "*" in the inbound telephone number specifies that a call can be
 accepted on any number.
 
 C) Establishment of a MLPPP connection
 --------------------------------------
 
 - please open the isdn-mppp file in the examples directory and follow along...
-	
-	This file is a script used to configure a BRI ISDN TA to accept a 
-	Multi Link PPP connection. 
-	
-	i)   using the isdnctrl utility, add an interface with "addif" and 
+
+	This file is a script used to configure a BRI ISDN TA to accept a
+	Multi Link PPP connection.
+
+	i)   using the isdnctrl utility, add an interface with "addif" and
 	     name it "ippp0"
 	ii)  add the inbound telephone number
-	iii) set the Layer 2 protocol to hdlc and the Layer 3 protocol to 
+	iii) set the Layer 2 protocol to hdlc and the Layer 3 protocol to
 	     trans (transparent)
 	iv)  set the packet encapsulation to syncppp
-	v)   set the eaz of the interface to be the phone number of that 
+	v)   set the eaz of the interface to be the phone number of that
 	     specific channel
 	vi)  to turn the callback features off, set the callback to "off" and
 	     the callback delay (cbdelay) to 0.
 	vi)  the hangup timeout can be set to a specified number of seconds
-	vii) the hangup upon incoming call can be set on or off 
+	vii) the hangup upon incoming call can be set on or off
 	viii) add a slave interface and name it "ippp32" for example
 	ix)  set the similar parameters for the ippp32 interface
-	x)   use the ifconfig command to bring-up the ippp0 interface with a 
+	x)   use the ifconfig command to bring-up the ippp0 interface with a
 	     specific IP address and point to point address
 	xi)  add a route to the IP address through the ippp0 interface
 	xii) use the ipppd function found in /sbin/ipppd to set the following:
@@ -261,11 +261,11 @@ C) Establishment of a MLPPP connection
 	xv)  add (+) the multi-link function "+mp"
 	xvi)  link the two /dev interfaces to the daemon
 
-NOTE:  To use the MLPPP connection to dial OUT to a MLPPP connection, change 
-the inbound telephone numbers to the outgoing telephone numbers of the MLPPP 
+NOTE:  To use the MLPPP connection to dial OUT to a MLPPP connection, change
+the inbound telephone numbers to the outgoing telephone numbers of the MLPPP
 host.
 
-	
+
 3. Beta Change Summaries and Miscellaneous Notes
 ------------------------------------------------
 When using the "scctrl" utility to upload firmware revisions on the board,
-- 
1.7.1.251.gf80a2

[PATCH 062/199] Documentation/isdn/README.x25: Checkpatch cleanup

[Andrea Gelmini]

Documentation/isdn/README.x25:1: ERROR: trailing whitespace
Documentation/isdn/README.x25:25: ERROR: trailing whitespace
Documentation/isdn/README.x25:26: ERROR: trailing whitespace
Documentation/isdn/README.x25:31: ERROR: trailing whitespace
Documentation/isdn/README.x25:33: ERROR: trailing whitespace
Documentation/isdn/README.x25:75: ERROR: trailing whitespace
Documentation/isdn/README.x25:143: ERROR: trailing whitespace
Documentation/isdn/README.x25:152: ERROR: trailing whitespace
Documentation/isdn/README.x25:162: ERROR: trailing whitespace
Documentation/isdn/README.x25:182: ERROR: trailing whitespace

Signed-off-by: Andrea Gelmini <andrea.gelmini@gelma.net>
---
 Documentation/isdn/README.x25 |   19 +++++++++----------
 1 files changed, 9 insertions(+), 10 deletions(-)

diff --git a/Documentation/isdn/README.x25 b/Documentation/isdn/README.x25
index e561a77..c6fe709 100644
--- a/Documentation/isdn/README.x25
+++ b/Documentation/isdn/README.x25
@@ -1,4 +1,3 @@
-  
 X.25 support within isdn4linux
 ==============================
 
@@ -22,15 +21,15 @@ more bugs as usual.
 
 - Monitor your isdn connections while using this software. This should
   prevent you from undesired phone bills in case of driver problems.
-  
- 
+
+
 
 
 How to configure the kernel
 ===========================
- 
+
 The ITU-T (former CCITT) X.25 network protocol layer has been implemented
-in the Linux source tree since version 2.1.16. The isdn subsystem might be 
+in the Linux source tree since version 2.1.16. The isdn subsystem might be
 useful to run X.25 on top of ISDN. If you want to try it, select
 
    "CCITT X.25 Packet Layer"
@@ -72,7 +71,7 @@ X.25 on top of isdn might be useful with two different scenarios:
   also allows using the D-channel) is not supported by isdn4linux.
   It should however be possible to establish such packet mode connections
   with certain active isdn cards provided that the firmware supports X.31
-  and the driver exports this functionality to the user. Currently, 
+  and the driver exports this functionality to the user. Currently,
   the AVM B1 driver is the only driver which does so. (It should be
   possible to access D-channel X.31 with active AVM cards using the
   CAPI interface of the AVM-B1 driver).
@@ -140,7 +139,7 @@ To test X.25 on top of isdn, you need to get
 - a recent version of the "isdnctrl" program that supports setting the new
   X.25 specific parameters.
 
-- the x25-utils-2.X package from 
+- the x25-utils-2.X package from
   ftp://ftp.hes.iki.fi/pub/ham/linux/ax25/x25utils-*
   (don't confuse the x25-utils with the ax25-utils)
 
@@ -149,7 +148,7 @@ To test X.25 on top of isdn, you need to get
 
 Before compiling the user level utilities make sure that the compiler/
 preprocessor will fetch the proper kernel header files of this kernel
-source tree. Either make /usr/include/linux a symbolic link pointing to 
+source tree. Either make /usr/include/linux a symbolic link pointing to
 this kernel's include/linux directory or set the appropriate compiler flags.
 
 When all drivers and interfaces are loaded and configured you need to
@@ -159,7 +158,7 @@ the usual ifconfig tool.
 ifconfig <iface-name> up
 
 But a special x25route tool (distributed with the x25-util package)
-is needed to set up X.25 routes. I.e. 
+is needed to set up X.25 routes. I.e.
 
 x25route add 01 <iface-name>
 
@@ -179,6 +178,6 @@ provide useful examples for setting up X.25 on top of isdn.
 
 The x25-utility package also contains an x25trace tool that can be
 used to monitor X.25 packets received by the network interfaces.
-The /proc/net/x25* files also contain useful information. 
+The /proc/net/x25* files also contain useful information.
 
 - Henner
-- 
1.7.1.251.gf80a2

[PATCH 063/199] Documentation/isdn/syncPPP.FAQ: Checkpatch cleanup

[Andrea Gelmini]

Documentation/isdn/syncPPP.FAQ:1: ERROR: trailing whitespace
Documentation/isdn/syncPPP.FAQ:8: ERROR: trailing whitespace
Documentation/isdn/syncPPP.FAQ:13: ERROR: trailing whitespace
Documentation/isdn/syncPPP.FAQ:15: ERROR: trailing whitespace
Documentation/isdn/syncPPP.FAQ:29: ERROR: trailing whitespace
Documentation/isdn/syncPPP.FAQ:38: ERROR: trailing whitespace
Documentation/isdn/syncPPP.FAQ:41: ERROR: trailing whitespace
Documentation/isdn/syncPPP.FAQ:42: ERROR: trailing whitespace
Documentation/isdn/syncPPP.FAQ:51: ERROR: trailing whitespace
Documentation/isdn/syncPPP.FAQ:58: ERROR: trailing whitespace
Documentation/isdn/syncPPP.FAQ:63: ERROR: trailing whitespace
Documentation/isdn/syncPPP.FAQ:64: ERROR: trailing whitespace
Documentation/isdn/syncPPP.FAQ:67: ERROR: trailing whitespace
Documentation/isdn/syncPPP.FAQ:72: ERROR: trailing whitespace
Documentation/isdn/syncPPP.FAQ:77: ERROR: trailing whitespace
Documentation/isdn/syncPPP.FAQ:82: ERROR: trailing whitespace
Documentation/isdn/syncPPP.FAQ:109: ERROR: trailing whitespace
Documentation/isdn/syncPPP.FAQ:130: ERROR: trailing whitespace
Documentation/isdn/syncPPP.FAQ:139: ERROR: trailing whitespace
Documentation/isdn/syncPPP.FAQ:141: ERROR: trailing whitespace
Documentation/isdn/syncPPP.FAQ:152: ERROR: trailing whitespace
Documentation/isdn/syncPPP.FAQ:162: ERROR: trailing whitespace
Documentation/isdn/syncPPP.FAQ:181: ERROR: trailing whitespace
Documentation/isdn/syncPPP.FAQ:184: ERROR: trailing whitespace
Documentation/isdn/syncPPP.FAQ:207: ERROR: trailing whitespace
Documentation/isdn/syncPPP.FAQ:217: ERROR: trailing whitespace

Signed-off-by: Andrea Gelmini <andrea.gelmini@gelma.net>
---
 Documentation/isdn/syncPPP.FAQ |   52 ++++++++++++++++++++--------------------
 1 files changed, 26 insertions(+), 26 deletions(-)

diff --git a/Documentation/isdn/syncPPP.FAQ b/Documentation/isdn/syncPPP.FAQ
index 3257a4b..bf4d912 100644
--- a/Documentation/isdn/syncPPP.FAQ
+++ b/Documentation/isdn/syncPPP.FAQ
@@ -1,18 +1,18 @@
-simple isdn4linux PPP FAQ .. to be continued .. not 'debugged' 
+simple isdn4linux PPP FAQ .. to be continued .. not 'debugged'
 -------------------------------------------------------------------
 
 Q01: what's pppd, ipppd, syncPPP, asyncPPP ??
 Q02: error message "this system lacks PPP support"
 Q03: strange information using 'ifconfig'
 Q04: MPPP?? What's that and how can I use it ...
-Q05: I tried MPPP but it doesn't work 
+Q05: I tried MPPP but it doesn't work
 Q06: can I use asynchronous PPP encapsulation with network devices
 Q07: A SunISDN machine can't connect to my i4l system
 Q08: I wanna talk to several machines, which need different configs
 Q09: Starting the ipppd, I get only error messages from i4l
-Q10: I wanna use dynamic IP address assignment 
+Q10: I wanna use dynamic IP address assignment
 Q11: I can't connect. How can I check where the problem is.
-Q12: How can I reduce login delay? 
+Q12: How can I reduce login delay?
 
 -------------------------------------------------------------------
 
@@ -26,7 +26,7 @@ A: The pppd is for asynchronous PPP .. asynchronous means
    frames (bit based protocol) ... The PPP driver
    in isdn4linux pushes all IP packets direct
    to the network layer and all PPP protocol
-   frames to the /dev/ippp* device. 
+   frames to the /dev/ippp* device.
    So, the ipppd is a simple external network
    protocol handler.
 
@@ -35,11 +35,11 @@ A: The pppd is for asynchronous PPP .. asynchronous means
    remote terminal server -> use the 'old' pppd
 
    If your remote side immediately starts to send
-   frames ... you probably connect to a 
+   frames ... you probably connect to a
    syncPPP machine .. use the network device part
    of isdn4linux with the 'syncppp' encapsulation
-   and make sure, that the ipppd is running and 
-   connected to at least one /dev/ippp*. Check the 
+   and make sure, that the ipppd is running and
+   connected to at least one /dev/ippp*. Check the
    isdn4linux manual on how to configure a network device.
 
 --
@@ -48,38 +48,38 @@ Q02: when I start the ipppd .. I only get the
    error message "this system lacks PPP support"
 A: check that at least the device 'ippp0' exists.
    (you can check this e.g with the program 'ifconfig')
-   The ipppd NEEDS this device under THIS name .. 
+   The ipppd NEEDS this device under THIS name ..
    If this device doesn't exists, use:
 	isdnctrl addif ippp0
 	isdnctrl encap ippp0 syncppp
 	... (see isdn4linux doc for more) ...
 A: Maybe you have compiled the ipppd with another
    kernel source tree than the kernel you currently
-   run ... 
+   run ...
 
 --
 
 Q03: when I list the netdevices with ifconfig I see, that
-   my ISDN interface has a HWaddr and IRQ=0 and Base 
-   address = 0 
+   my ISDN interface has a HWaddr and IRQ=0 and Base
+   address = 0
 A: The device is a fake ethernet device .. ignore IRQ and baseaddr
    You need the HWaddr only for ethernet encapsulation.
-   
+
 --
 
 Q04: MPPP?? What's that and how can I use it ...
 
-A: MPPP or MP or MPP (Warning: MP is also an 
+A: MPPP or MP or MPP (Warning: MP is also an
    acronym for 'Multi Processor') stands for
    Multi Point to Point and means bundling
    of several channels to one logical stream.
    To enable MPPP negotiation you must call the
-   ipppd with the '+mp' option. 
+   ipppd with the '+mp' option.
    You must also configure a slave device for
    every additional channel. (see the i4l manual
    for more)
    To use channel bundling you must first activate
-   the 'master' or initial call. Now you can add 
+   the 'master' or initial call. Now you can add
    the slave channels with the command:
        isdnctrl addlink <device>
    e.g:
@@ -106,7 +106,7 @@ Q06: can I use asynchronous PPP encapsulation
 A: No .. that's not possible .. Use the standard
    PPP package over the /dev/ttyI* devices. You
    must not use the ipppd for this.
-   
+
 --
 
 Q07: A SunISDN machine tries to connect my i4l system,
@@ -127,7 +127,7 @@ Q08: I wanna talk to remote machines, which need
    a different configuration. The only way
    I found to do this is to kill the ipppd and
    start a new one with another config to connect
-   to the second machine. 
+   to the second machine.
 
 A: you must bind a network interface explicitly to
    an ippp device, where you can connect a (for this
@@ -136,9 +136,9 @@ A: you must bind a network interface explicitly to
 --
 
 Q09: When I start the ipppd I only get error messages
-   from the i4l driver .. 
+   from the i4l driver ..
 
-A: When starting, the ipppd calls functions which may 
+A: When starting, the ipppd calls functions which may
    trigger a network packet. (e.g gethostbyname()).
    Without the ipppd (at this moment, it is not
    fully started) we can't handle this network request.
@@ -149,7 +149,7 @@ A: When starting, the ipppd calls functions which may
 
 --
 
-Q10: I wanna use dynamic IP address assignment ... How 
+Q10: I wanna use dynamic IP address assignment ... How
    must I configure the network device.
 
 A: At least you must have a route which forwards
@@ -159,7 +159,7 @@ A: At least you must have a route which forwards
    Now you must choose a dummy IP address for your
    interface.
    If for some reason you can't set the default
-   route to the ippp interface, you may take any 
+   route to the ippp interface, you may take any
    address of the subnet from which you expect your
    dynamic IP number and set a 'network route' for
    this subnet to the ippp interface.
@@ -178,10 +178,10 @@ A: You must know, how the ipppd gets the addresses it wanna
    If your side doesn't know the IP address after negotiation, it
    closes the connection!
    You must allow overriding of address with the 'ipcp-accept-*'
-   options, if you have set your own or the remote address 
+   options, if you have set your own or the remote address
    explicitly.
 
-A: Maybe you try these options .. e.g:   
+A: Maybe you try these options .. e.g:
 
     /sbin/ipppd :$REMOTE noipdefault /dev/ippp0
 
@@ -204,7 +204,7 @@ A: A good help log is the debug output from the ipppd...
         you can see, whether there is activity on the card/line.
    - there are at least a few RECV messages in the log:
      -> fine: your card is dialing and your remote machine
-        tries to talk with you. Maybe only a missing 
+        tries to talk with you. Maybe only a missing
         authentication. Check your ipppd configuration again.
    - the ipppd exits for some reason:
      -> not good ... check /var/adm/syslog and /var/adm/daemon.
@@ -214,7 +214,7 @@ A: A good help log is the debug output from the ipppd...
 
 Q12: How can I reduce login delay?
 
-A: Log a login session ('debug' log) and check which options 
+A: Log a login session ('debug' log) and check which options
   your remote side rejects. Next time configure your ipppd
   to not negotiate these options. Another 'side effect' is, that
   this increases redundancy. (e.g your remote side is buggy and
-- 
1.7.1.251.gf80a2