From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
DRI Development <dri-devel@lists.freedesktop.org>
Cc: Plagniol-Villard <plagnioj@jcrosoft.com>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 1/2] video/fbdev: Always built-in video= cmdline parsing
Date: Tue, 30 Sep 2014 11:40:47 +0000 [thread overview]
Message-ID: <542A96BF.7080303@ti.com> (raw)
In-Reply-To: <1407329562-10832-1-git-send-email-daniel.vetter@ffwll.ch>
[-- Attachment #1: Type: text/plain, Size: 1641 bytes --]
Hi,
On 06/08/14 15:52, Daniel Vetter wrote:
> In drm/i915 we want to get at the video= cmdline modes even when we
> don't have fbdev support enabled, so that users can always override
> the kernel's initial mode selection.
>
> But that gives us a direct depency upon the parsing code in the fbdev
> subsystem. Since it's so little code just extract these 2 functions
> and always build them in.
>
> Whiel at it fix the checkpatch fail in this code.
>
> v2: Also move fb_mode_option. Spotted by the kbuild.
>
> v3: Review from Geert:
> - Keep the old copyright notice from fb_mem.c, although I have no
> idea what exactly applies.
> - Only compile this when needed.
>
> Cc: Geert Uytterhoeven <geert@linux-m68k.org>
> Cc: Plagniol-Villard <plagnioj@jcrosoft.com>
> Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
> Cc: linux-fbdev@vger.kernel.org
> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>
> --
>
> I prefer if we can merge this through drm-next since we'll use it
> there in follow-up patches.
> -Daniel
> ---
> drivers/video/fbdev/Kconfig | 4 ++
> drivers/video/fbdev/core/Makefile | 1 +
> drivers/video/fbdev/core/fb_cmdline.c | 110 ++++++++++++++++++++++++++++++++++
> drivers/video/fbdev/core/fbmem.c | 92 ----------------------------
> drivers/video/fbdev/core/modedb.c | 3 -
> 5 files changed, 115 insertions(+), 95 deletions(-)
> create mode 100644 drivers/video/fbdev/core/fb_cmdline.c
Sorry for late response.
Looks fine for me, and I'm fine merging it via drm-next.
Acked-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-09-30 11:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1407312512-6533-1-git-send-email-daniel.vetter@ffwll.ch>
2014-08-06 9:43 ` [PATCH] video/fbdev: Always built-in video= cmdline parsing Daniel Vetter
2014-08-06 10:27 ` Geert Uytterhoeven
2014-08-06 12:48 ` Daniel Vetter
2014-08-06 12:05 ` Daniel Vetter
2014-08-06 12:52 ` [PATCH 1/2] " Daniel Vetter
2014-09-30 11:40 ` Tomi Valkeinen [this message]
2014-09-30 11:53 ` Daniel Vetter
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=542A96BF.7080303@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=plagnioj@jcrosoft.com \
/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).