From: Matthew Wilcox <matthew@wil.cx>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] Documentation: Correct "dmascc=" to read "dmascc.io=".
Date: Sun, 09 Sep 2007 06:46:51 +0000 [thread overview]
Message-ID: <20070909064650.GE6809@parisc-linux.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0709090218210.20776@localhost.localdomain>
On Sun, Sep 09, 2007 at 02:19:44AM -0400, Robert P. J. Day wrote:
> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
> index b41cde3..318b284 100644
> --- a/Documentation/kernel-parameters.txt
> +++ b/Documentation/kernel-parameters.txt
> @@ -543,7 +543,7 @@ 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
> + dmascc.io= [HW,AX25,SERIAL] AX.25 Z80SCC driver with DMA
> support available.
> Format: <io_dev0>[,<io_dev1>[,..<io_dev32>]]
>
It's not clear to me that this should be mentioned in
kernel-parameters.txt. Many, many drivers have options which could be
mentioned in kernel-parameters.txt, and yet are not.
> diff --git a/drivers/net/hamradio/Kconfig b/drivers/net/hamradio/Kconfig
> index 36d2c7d..62d5d5c 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 "dmasccdr1,addr2,..." (when compiled into the
> + to be probed by "dmascc.iodr1,addr2,..." (when compiled into the
> kernel image) or "iodr1,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.
Makes sense to mention it in the Kconfig text here though.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
-
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-09-09 6:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-09 6:19 [PATCH] Documentation: Correct "dmascc=" to read "dmascc.io=" Robert P. J. Day
2007-09-09 6:46 ` Matthew Wilcox [this message]
2007-09-09 7:01 ` Robert P. J. Day
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070909064650.GE6809@parisc-linux.org \
--to=matthew@wil.cx \
--cc=kernel-janitors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.