All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/2] Enable video in the rk3399-puma defconfig (includes rk_hdmi.c fix for compile warning)
Date: Tue,  6 Jun 2017 09:15:13 +0200	[thread overview]
Message-ID: <1496733316-9788-1-git-send-email-philipp.tomsich@theobroma-systems.com> (raw)


If our defconfig update to enable HDMI output for the RK3399-Q7 is
applied before my patch-series refactoring the rk_hdmi/rk_vop and
adding RK3399 support, compilers will raise warnings due to a missing
include-directive in the original rk_hdmi.c.

As the VOP/HDMI changes are propagating through Anatolij's tree and
the defconfig update through Simon's tree, this series bundles a fix
for the older rk_hdmi.c version with the defconfig update to allow
these changesets to be applied in any order.


Changes in v3:
- adds an include-directive to the (pre-RK3399 enabled) rk_hdmi to
  fix implicit definition warnings

Changes in v2:
- enable CMD_BMP in the puma-rk3399_defconfig (following a rebase to
  the upstream master after CMD_BMP was migrate to Kconfig)

Philipp Tomsich (2):
  rockchip: video: rk_hdmi: fix implicit definition warnings
  rockchip: defconfig: puma-rk3399: update defconfig with video-support

 configs/puma-rk3399_defconfig    | 8 ++++++++
 drivers/video/rockchip/rk_hdmi.c | 1 +
 2 files changed, 9 insertions(+)

-- 
1.9.1

             reply	other threads:[~2017-06-06  7:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06  7:15 Philipp Tomsich [this message]
2017-06-06  7:15 ` [U-Boot] [PATCH 1/2] rockchip: video: rk_hdmi: fix implicit definition warnings Philipp Tomsich
2017-06-06 21:09   ` Simon Glass
2017-06-08  3:34     ` sjg at google.com
2017-06-06  7:15 ` [U-Boot] [PATCH 2/2] rockchip: defconfig: puma-rk3399: update defconfig with video-support Philipp Tomsich
2017-06-06 21:09   ` Simon Glass
2017-06-08  3:34     ` sjg at google.com

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=1496733316-9788-1-git-send-email-philipp.tomsich@theobroma-systems.com \
    --to=philipp.tomsich@theobroma-systems.com \
    --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.