public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: root <thunder7@xs4all.nl>
To: linux-fb-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: uvesafb in 2.6.27-rc9 uses mode_option, in 2.6.27 mode, but the docs aren't updated
Date: Tue, 7 Oct 2008 18:54:10 +0000	[thread overview]
Message-ID: <20081007185410.GA7872@onderneming10> (raw)

I just tested 2.6.27-rc9 on my laptop, which uses uvesafb. I notice that
I need to update

/sbin/modprobe uvesafb mode=1400x1050

to

/sbin/modprobe uvesafb mode_option=1400x1050

but the documentation in Documentation/fb/uvesafb.txt happily talks
about the mode option. It would be nice to have the documentation
updated at least, but might I also question this move at all? Why call
something 'mode_option' when 'mode' is shorter and the fact that it's an
option really is clear from the fact you mention it on the commandline,
like, how-do-I-call-it, yes-I-remember, an option?

Or are we moving toward 'mtrr_option', 'scroll_option',
'vram_remap_option' etc? I don't think that really a good idea, so the
easiest thing to do would be to revert the patch that did this rename,
since that resyncs the Documentation to the actual module and removes
the needless description of the 'mode' option.

Kind regards,
Jurriaan

             reply	other threads:[~2008-10-07 19:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-07 18:54 root [this message]
2008-10-09 17:56 ` [PATCH] docs: Re: uvesafb in 2.6.27-rc9 uses mode_option, in 2.6.27 mode, but the docs aren't updated 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=20081007185410.GA7872@onderneming10 \
    --to=thunder7@xs4all.nl \
    --cc=linux-fb-devel@lists.sourceforge.net \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox