From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [PATCH 0/5] video: Avoid #ifdef to increase build coverage
Date: Sat, 4 Jan 2020 11:45:29 +0100 [thread overview]
Message-ID: <20200104114529.76b4ecb7@crub> (raw)
In-Reply-To: <20191221011037.143972-1-sjg@chromium.org>
Hi Simon,
On Fri, 20 Dec 2019 18:10:32 -0700
Simon Glass sjg at chromium.org wrote:
...
> Simon Glass (5):
> video: x86: Enable 32-bit graphics by default
> video: Avoid using #ifdef in video blitting code
> video: Avoid using #ifdef in console_rotate.c
> video: Avoid using #ifdef in vidconsole-uclass.c
> video: Avoid using #ifdef in video-uclass.c
>
> drivers/video/Kconfig | 5 +-
> drivers/video/console_normal.c | 125 ++++++------
> drivers/video/console_rotate.c | 325 +++++++++++++++---------------
> drivers/video/vidconsole-uclass.c | 22 +-
> drivers/video/video-uclass.c | 54 +++--
> 5 files changed, 256 insertions(+), 275 deletions(-)
Series applied to u-boot-video/master, thanks!
--
Anatolij
prev parent reply other threads:[~2020-01-04 10:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-21 1:10 [PATCH 0/5] video: Avoid #ifdef to increase build coverage Simon Glass
2019-12-21 1:10 ` [PATCH 1/5] video: x86: Enable 32-bit graphics by default Simon Glass
[not found] ` <20200102153306.59fd28f9@crub>
2020-01-03 2:29 ` Simon Glass
2020-01-03 2:41 ` Bin Meng
2020-01-03 3:24 ` Simon Glass
2020-01-03 15:41 ` Bin Meng
2020-01-03 16:16 ` Anatolij Gustschin
2019-12-21 1:10 ` [PATCH 2/5] video: Avoid using #ifdef in video blitting code Simon Glass
2019-12-21 1:10 ` [PATCH 3/5] video: Avoid using #ifdef in console_rotate.c Simon Glass
2019-12-21 1:10 ` [PATCH 4/5] video: Avoid using #ifdef in vidconsole-uclass.c Simon Glass
2019-12-21 1:10 ` [PATCH 5/5] video: Avoid using #ifdef in video-uclass.c Simon Glass
2020-01-04 10:45 ` Anatolij Gustschin [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=20200104114529.76b4ecb7@crub \
--to=agust@denx.de \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.