Documentation: Fix erroneous "dmascc=" documentation

Signed-off-by: Robert P. J. Day <rpjday@mindspring.com>
Signed-off-by: Adrian Bunk <bunk@kernel.org>

2 files changed, 1 insertions, 5 deletions

diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
index 3ea49f98d405..c80ad89080b8 100644
--- a/Documentation/kernel-parameters.txt
+++ b/Documentation/kernel-parameters.txt
@@ -564,10 +564,6 @@ and is between 256 and 4096 characters. It is defined in the file
                         See drivers/char/README.epca and
                         Documentation/digiepca.txt.
 
-        dmascc=         [HW,AX25,SERIAL] AX.25 Z80SCC driver with DMA
-                        support available.
-                        Format: <io_dev0>[,<io_dev1>[,..<io_dev32>]]
-
         dmasound=       [HW,OSS] Sound subsystem buffers
 
         dscc4.setup=    [NET]
diff --git a/drivers/net/hamradio/Kconfig b/drivers/net/hamradio/Kconfig
index 36d2c7d4f4d0..62d5d5cfd6a6 100644
--- a/drivers/net/hamradio/Kconfig
+++ b/drivers/net/hamradio/Kconfig
@@ -64,7 +64,7 @@ config DMASCC
           dmascc. If you don't pass any parameter to the driver, all
           possible I/O addresses are probed. This could irritate other devices
           that are currently not in use. You may specify the list of addresses
-          to be probed by "dmascc=addr1,addr2,..." (when compiled into the
+          to be probed by "dmascc.io=addr1,addr2,..." (when compiled into the
           kernel image) or "io=addr1,addr2,..." (when loaded as a module). The
           network interfaces will be called dmascc0 and dmascc1 for the board
           detected first, dmascc2 and dmascc3 for the second one, and so on.