From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: Please pull u-boot-video
Date: Thu, 18 Jun 2020 23:12:46 +0200 [thread overview]
Message-ID: <20200618231246.27bdc80a@crub> (raw)
Hi Tom,
please pull some fixes for v2020.07-rc4. Thanks!
gitlab CI: https://gitlab.denx.de/u-boot/custodians/u-boot-video/pipelines/3720
The following changes since commit 9cb895203a46654f7ee6dd95be5c8ab05e4dfbd3:
Merge tag 'u-boot-stm32-20200616' of https://gitlab.denx.de/u-boot/custodians/u-boot-stm (2020-06-16 09:18:56 -0400)
are available in the Git repository at:
https://gitlab.denx.de/u-boot/custodians/u-boot-video.git tags/fixes-for-v2020.07-rc4
for you to fetch changes up to 1099b2abef35c3c887f6afac1a8ef18c7924d5d2:
colibri_imx6: fix video stdout in default environment (2020-06-18 19:17:28 +0200)
----------------------------------------------------------------
- fix stdout in default environment for apalis_imx6, colibri_imx6
and cm_fx6 boards
----------------------------------------------------------------
Anatolij Gustschin (3):
cm_fx6: fix video stdout in default environment
apalis_imx6: fix video stdout in default environment
colibri_imx6: fix video stdout in default environment
include/configs/apalis_imx6.h | 3 ++-
include/configs/cm_fx6.h | 4 ++--
include/configs/colibri_imx6.h | 3 ++-
3 files changed, 6 insertions(+), 4 deletions(-)
next reply other threads:[~2020-06-18 21:12 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 21:12 Anatolij Gustschin [this message]
2020-06-19 13:24 ` Please pull u-boot-video Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2023-10-23 10:17 Anatolij Gustschin
2023-10-23 16:58 ` Tom Rini
2023-08-14 6:02 Anatolij Gustschin
2023-08-14 15:04 ` Tom Rini
2023-08-01 12:52 Anatolij Gustschin
2023-08-01 15:57 ` Tom Rini
2023-07-16 20:04 Anatolij Gustschin
2023-07-17 14:38 ` Tom Rini
2023-05-05 8:25 Anatolij Gustschin
2023-05-05 17:14 ` Tom Rini
2023-04-07 19:51 Anatolij Gustschin
2023-04-08 18:18 ` Tom Rini
2023-02-04 19:09 Anatolij Gustschin
2023-02-06 14:55 ` Tom Rini
2022-10-30 21:16 Anatolij Gustschin
2022-10-31 12:52 ` Tom Rini
2022-06-25 7:34 Anatolij Gustschin
2022-06-25 15:57 ` Tom Rini
2022-03-14 22:33 Anatolij Gustschin
2022-03-15 12:13 ` Tom Rini
2022-03-19 17:05 ` Anatolij Gustschin
2022-03-19 17:44 ` Tom Rini
2022-03-19 17:55 ` Anatolij Gustschin
2021-12-28 14:25 Anatolij Gustschin
2021-12-28 16:26 ` Tom Rini
2021-10-09 21:29 Anatolij Gustschin
2021-10-10 20:04 ` Tom Rini
2021-08-05 22:01 Anatolij Gustschin
2021-08-06 21:22 ` Tom Rini
2021-06-05 13:00 Anatolij Gustschin
2021-06-07 11:21 ` Tom Rini
2021-04-24 14:33 Anatolij Gustschin
2021-04-24 21:42 ` Tom Rini
2021-04-10 21:21 Anatolij Gustschin
2021-04-11 18:10 ` Tom Rini
2021-03-19 8:02 Anatolij Gustschin
2021-03-19 12:21 ` Tom Rini
2021-02-22 12:17 Anatolij Gustschin
2021-02-22 17:32 ` Tom Rini
2020-10-26 20:43 Anatolij Gustschin
2020-10-27 14:50 ` Tom Rini
2020-10-27 19:37 ` Anatolij Gustschin
2020-10-27 19:43 ` Tom Rini
2020-10-27 19:47 ` Anatolij Gustschin
2020-10-18 20:36 Anatolij Gustschin
2020-10-19 21:17 ` Tom Rini
2020-08-04 7:42 Anatolij Gustschin
2020-08-04 20:55 ` Tom Rini
2020-06-29 19:50 Anatolij Gustschin
2020-06-29 19:58 ` Tom Rini
2020-06-28 12:27 Anatolij Gustschin
2020-06-29 1:30 ` Tom Rini
2020-04-27 8:32 Anatolij Gustschin
2020-04-27 16:20 ` Tom Rini
2020-04-02 16:13 Anatolij Gustschin
2020-04-02 16:18 ` Anatolij Gustschin
2020-04-05 23:04 ` Tom Rini
2020-02-10 17:07 Anatolij Gustschin
2020-02-10 19:16 ` Tom Rini
2020-01-18 16:19 Anatolij Gustschin
2020-01-18 16:28 ` Tom Rini
[not found] <20200102205451.4123cbe9@crub>
2020-01-03 14:46 ` Tom Rini
2019-12-10 20:38 Anatolij Gustschin
2019-12-11 13:15 ` Tom Rini
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=20200618231246.27bdc80a@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.