From: Anatolij Gustschin <agust@denx.de>
To: Tom Rini <trini@konsulko.com>
Cc: u-boot <u-boot@lists.denx.de>
Subject: Please pull u-boot-video
Date: Mon, 14 Aug 2023 08:02:54 +0200 [thread overview]
Message-ID: <20230814080254.1be1094e@crub> (raw)
Hi Tom,
please pull video driver fixes for for v2023.10.
CI: https://source.denx.de/u-boot/custodians/u-boot-video/-/pipelines/17338
Thanks,
Anatolij
The following changes since commit a5899cc69a99379f01e8e2f9f98e0e09b24f1656:
Merge https://source.denx.de/u-boot/custodians/u-boot-watchdog (2023-08-10 11:40:09 -0400)
are available in the Git repository at:
https://source.denx.de/u-boot/custodians/u-boot-video.git tags/video-20230814
for you to fetch changes up to 04cc66c047d959dc1b22a625b7949a26793ac52b:
rpi: set the correct parameter for simple framebuffer node (2023-08-13 23:57:46 +0200)
----------------------------------------------------------------
- fix NULL dereference in vidconsole_measure()
- fix simplefb format for raspberrypi-4b
- fix typo in Kconfig
----------------------------------------------------------------
Bin Meng (2):
video: vidconsole: Fix null dereference of ops->measure
video: kconfig: Fix a typo in SPL_VIDEO_REMOVE
Jason Wessel (1):
bcm2835: Add simiple-framebuffer for use with fkms
Meng Li (1):
rpi: set the correct parameter for simple framebuffer node
board/raspberrypi/rpi/rpi.c | 2 ++
drivers/video/Kconfig | 2 +-
drivers/video/bcm2835.c | 3 +++
drivers/video/vidconsole-uclass.c | 2 +-
4 files changed, 7 insertions(+), 2 deletions(-)
next reply other threads:[~2023-08-14 6:02 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 6:02 Anatolij Gustschin [this message]
2023-08-14 15:04 ` 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-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-06-18 21:12 Anatolij Gustschin
2020-06-19 13:24 ` 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=20230814080254.1be1094e@crub \
--to=agust@denx.de \
--cc=trini@konsulko.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.