From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: linux-fbdev@vger.kernel.org,
DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] fbdev: fix modedb docs in fb_find_mode
Date: Tue, 24 Jul 2018 15:37:47 +0000 [thread overview]
Message-ID: <4081544.2AHJ8dQMet@amdc3058> (raw)
In-Reply-To: <20180705135217.12561-1-daniel.vetter@ffwll.ch>
On Thursday, July 05, 2018 03:52:17 PM Daniel Vetter wrote:
> Fix up the indenting that confused sphinx. To make sure we
> don't have to make the examples unreadable with escaping just
> put them in as block quotes, that seems the simplest solution.
>
> Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
> Cc: linux-fbdev@vger.kernel.org
> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Patch queued for 4.19, thanks.
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
prev parent reply other threads:[~2018-07-24 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180705135225epcas4p1d94d7ea1f6de55f5f5430b3f8065b88b@epcas4p1.samsung.com>
2018-07-05 13:52 ` [PATCH] fbdev: fix modedb docs in fb_find_mode Daniel Vetter
2018-07-24 15:37 ` Bartlomiej Zolnierkiewicz [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=4081544.2AHJ8dQMet@amdc3058 \
--to=b.zolnierkie@samsung.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@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).