All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bin Meng <bmeng.cn@gmail.com>
To: Tom Rini <trini@konsulko.com>,
	U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Simon Glass <sjg@chromium.org>
Subject: Please pull u-boot-x86
Date: Tue, 1 Aug 2023 23:34:47 +0800	[thread overview]
Message-ID: <CAEUhbmU-g5yA8qsEGUqL-3BX7JL67TAPUv1CxpZLSL__xO6q-Q@mail.gmail.com> (raw)

Hi Tom,

CI: https://source.denx.de/u-boot/custodians/u-boot-x86/-/pipelines/17161

The following changes since commit 4e619e8d4fd68095bc665a78f2651d8e478a4534:

  Merge tag 'u-boot-rockchip-20230731' of
https://source.denx.de/u-boot/custodians/u-boot-rockchip (2023-07-31
11:33:51 -0400)

are available in the Git repository at:

  https://source.denx.de/u-boot/custodians/u-boot-x86.git tags/x86-pull-20230801

for you to fetch changes up to db971a7587d04b3f1cf2e6d452f9e37f50c5b3ed:

  x86: Add a little more info to cbsysinfo (2023-08-01 10:08:49 +0800)

----------------------------------------------------------------
- MTRR fixes for x86 boards
- Add a little more info to 'cbsysinfo' command

----------------------------------------------------------------
Bin Meng (5):
      x86: Change testing logic of mtrr commit
      x86: fsp: Use mtrr_set_next_var() for graphics memory
      video: broadwell: Use mtrr_set_next_var() for graphics memory
      video: ivybridge: Use mtrr_set_next_var() for graphics memory
      video: vesa: Use mtrr_set_next_var() for graphics memory

Simon Glass (2):
      x86: Return mtrr_add_request() to its old purpose
      x86: Add a little more info to cbsysinfo

 arch/x86/cpu/mtrr.c                |  6 +++++-
 arch/x86/include/asm/cb_sysinfo.h  |  4 ++++
 arch/x86/lib/coreboot/cb_sysinfo.c |  4 ++++
 arch/x86/lib/fsp/fsp_graphics.c    |  3 +--
 arch/x86/lib/init_helpers.c        |  6 ++----
 cmd/x86/cbsysinfo.c                |  5 +++--
 drivers/video/broadwell_igd.c      | 10 +++-------
 drivers/video/ivybridge_igd.c      |  3 +--
 drivers/video/vesa.c               |  3 +--
 9 files changed, 24 insertions(+), 20 deletions(-)

Regards,
Bin

             reply	other threads:[~2023-08-01 15:35 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01 15:34 Bin Meng [this message]
2023-08-01 16:03 ` Please pull u-boot-x86 Tom Rini
  -- strict thread matches above, loose matches on Subject: below --
2023-08-09 16:38 Bin Meng
2023-08-09 19:09 ` Tom Rini
2023-07-17 12:44 Bin Meng
2023-07-17 18:53 ` Tom Rini
2023-05-11  8:16 Bin Meng
2023-05-11 16:33 ` Tom Rini
2023-03-27  1:42 Bin Meng
2023-03-27 17:34 ` Tom Rini
2022-12-14  6:27 Bin Meng
2022-12-16 13:24 ` Tom Rini
2022-03-14 14:40 Bin Meng
2022-03-14 16:19 ` Tom Rini
2021-11-01  4:38 Bin Meng
2021-11-01 17:43 ` Tom Rini
2021-09-22 15:42 Bin Meng
2021-09-22 15:51 ` Tom Rini
2021-08-13  5:11 Bin Meng
2021-08-13 12:39 ` Tom Rini
2021-08-02 23:35 Bin Meng
2021-08-03 13:06 ` Tom Rini
2021-07-15 13:54 Bin Meng
2021-07-15 18:48 ` Tom Rini
2021-06-23 11:01 Bin Meng
2021-06-24 13:15 ` Tom Rini
2021-05-10 12:00 Bin Meng
2021-05-10 21:06 ` Tom Rini
2021-04-15  4:20 Bin Meng
2021-04-15 19:42 ` Tom Rini
2021-03-09  5:15 Bin Meng
2021-03-10  4:00 ` Tom Rini
2021-02-06 13:08 Bin Meng
2021-02-07 19:15 ` Tom Rini
2021-02-04  0:08 Bin Meng
2021-02-04 21:58 ` Tom Rini
2021-02-01  9:37 Bin Meng
2021-02-01 16:05 ` Tom Rini
2020-12-22  7:27 Bin Meng
2020-12-23 21:55 ` Tom Rini
2020-12-16  9:34 Bin Meng
2020-12-16 16:01 ` Tom Rini
2020-11-10  3:38 Bin Meng
2020-11-10 12:39 ` Tom Rini
2020-11-06  4:55 Bin Meng
2020-11-06 16:26 ` Tom Rini
2020-09-21 14:14 Bin Meng
2020-09-21 17:39 ` Tom Rini
2020-09-01 14:36 Bin Meng
2020-09-01 17:25 ` Tom Rini
2020-08-03  4:27 Bin Meng
2020-08-03 16:00 ` Tom Rini
2020-07-20  3:24 Bin Meng
2020-07-20 16:14 ` Tom Rini
2020-07-17 10:15 Bin Meng
2020-07-17 14:49 ` Tom Rini
2020-07-09  9:50 Bin Meng
2020-07-09 23:59 ` Tom Rini
2020-06-02  1:23 Bin Meng
2020-06-02 13:29 ` Tom Rini
2020-05-27  6:45 Bin Meng
2020-05-27 15:59 ` Tom Rini
2020-05-04  9:31 Bin Meng
2020-05-04 17:54 ` Tom Rini
2020-04-30 13:53 Bin Meng
2020-04-30 19:10 ` Tom Rini
2020-04-16 11:11 Bin Meng
2020-04-16 17:38 ` Tom Rini
2020-04-04 23:12 Bin Meng
2020-04-05 23:05 ` Tom Rini
2020-03-05 12:49 Bin Meng
2020-03-09 12:24 ` Tom Rini
2020-02-08  1:54 Bin Meng
2020-02-10 13:39 ` Tom Rini
2020-02-10 17:20   ` Anatolij Gustschin
2020-02-10 17:28     ` Tom Rini
2020-02-04  6:58 Bin Meng
2020-02-05  1:03 ` Tom Rini
2019-12-08 15:49 Bin Meng
2019-12-08 16:36 ` 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=CAEUhbmU-g5yA8qsEGUqL-3BX7JL67TAPUv1CxpZLSL__xO6q-Q@mail.gmail.com \
    --to=bmeng.cn@gmail.com \
    --cc=sjg@chromium.org \
    --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.