From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: Bernie Thompson <bernie@plugable.com>,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
Helge Deller <deller@gmx.de>, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: fb: udlfb: clean up text and formatting
Date: Sun, 28 Aug 2022 08:51:01 +0700 [thread overview]
Message-ID: <6cb3b3fc-30d4-0396-fc95-8182ca72fb1e@gmail.com> (raw)
In-Reply-To: <20220827193925.19612-1-rdunlap@infradead.org>
On 8/28/22 02:39, Randy Dunlap wrote:
> -From the command line, pass options to modprobe
> -modprobe udlfb fb_defio=0 console=1 shadow=1
> +From the command line, pass options to modprobe::
>
> -Or modify options on the fly at /sys/module/udlfb/parameters directory via
> -sudo nano fb_defio
> -change the parameter in place, and save the file.
> + modprobe udlfb fb_defio=0 console=1 shadow=1
> +
> +Or modify options on the fly at /sys/module/udlfb/parameters directory via::
> +
> + sudo nano fb_defio
> + change the parameter in place, and save the file.
>
Better say "Or change the options on the fly by editing
/sys/module/udlfb/parameters/fb_defio."
> Unplug/replug USB device to apply with new settings
>
> -Or for permanent option, create file like /etc/modprobe.d/udlfb.conf with text
> -options udlfb fb_defio=0 console=1 shadow=1
> +Or for permanent options, create a file like /etc/modprobe.d/udlfb.conf
> +with text::
> +
> + options udlfb fb_defio=0 console=1 shadow=1
Maybe we can say "Or to apply options permanently, create modprobe configuration
like /etc/modprobe.d/udlfb.conf with::"
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-08-28 1:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-27 19:39 [PATCH] Documentation: fb: udlfb: clean up text and formatting Randy Dunlap
2022-08-28 1:51 ` Bagas Sanjaya [this message]
2022-08-28 5:31 ` Randy Dunlap
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=6cb3b3fc-30d4-0396-fc95-8182ca72fb1e@gmail.com \
--to=bagasdotme@gmail.com \
--cc=bernie@plugable.com \
--cc=corbet@lwn.net \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).