From: Jonathan Corbet <corbet@lwn.net>
To: Jiri Slaby <jslaby@suse.cz>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH -resend] Documentation: fb, fix path to modedb.c
Date: Thu, 23 Jul 2020 13:58:29 -0600 [thread overview]
Message-ID: <20200723135829.35b44922@lwn.net> (raw)
In-Reply-To: <20200723103454.26167-1-jslaby@suse.cz>
On Thu, 23 Jul 2020 12:34:54 +0200
Jiri Slaby <jslaby@suse.cz> wrote:
> modedb.c was moved twice since the modedb documentation was written.
> Update the path to the current one.
>
> Signed-off-by: Jiri Slaby <jslaby@suse.cz>
> Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: dri-devel@lists.freedesktop.org
> Cc: linux-fbdev@vger.kernel.org
> Cc: linux-doc@vger.kernel.org
> ---
> Documentation/fb/modedb.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/fb/modedb.rst b/Documentation/fb/modedb.rst
> index 624d08fd2856..4d2411e32ebb 100644
> --- a/Documentation/fb/modedb.rst
> +++ b/Documentation/fb/modedb.rst
> @@ -152,7 +152,7 @@ To specify a video mode at bootup, use the following boot options::
> video=<driver>:<xres>x<yres>[-<bpp>][@refresh]
>
> where <driver> is a name from the table below. Valid default modes can be
> -found in linux/drivers/video/modedb.c. Check your driver's documentation.
> +found in drivers/video/fbdev/core/modedb.c. Check your driver's documentation.
> There may be more modes::
"resend" but I've never seen it before...in any case I've applied it now.
Thanks,
jon
prev parent reply other threads:[~2020-07-23 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 10:34 [PATCH -resend] Documentation: fb, fix path to modedb.c Jiri Slaby
2020-07-23 19:58 ` Jonathan Corbet [this message]
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=20200723135829.35b44922@lwn.net \
--to=corbet@lwn.net \
--cc=b.zolnierkie@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jslaby@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).